Open source · MIT · macOS

Every AI tool you use,
in one macOS window.

Chat with any model. Run a code agent. Design interfaces. Hand a goal to a team of agents and get real files back. Five tools in one window, one config. Your API keys stay on your Mac.

Apple Silicon · macOS 14+ · Free, no account, no telemetry

The problem

Your AI tools live in separate windows, with separate keys, that never talk to each other. You copy-paste between them and reconfigure the same model three times a day. OpenAxis ends that.

One window, not eight

Chat, code, design, work, and orchestration sit in a single native sidebar. Each opens in its own view and keeps its state when you switch.

One config, not five

Enter your API keys once. A local proxy holds them and feeds every tool. No per-app setup, no keys pasted into five settings panels.

One memory, not none

A shared profile, project context, and tagged facts follow you across every tool, so you stop re-explaining who you are and what you're building (under maintenance — coming soon).

The five tools

One sidebar. Five ways to create.

Two are built into OpenAxis. Three are mature open-source tools, wrapped without touching their source. Same keys, same theme, same memory.

Explore every tool in depth
What sets it apart

You give a goal. It gives you a finished project.

You get a folder of real, working files. Not a chat transcript.

The orchestrator is an interactive assistant. Type what you need in plain language — it plans the work as a visual DAG you can inspect: researchers, writers, designers, coders, verifiers, wired into a dependency graph. They execute in order, pass results downstream, and write real files to disk.

Here's what makes it real: a deterministic quality gate reads the output and force-fails on broken imports, missing files, dead links, or two agents that wrote incompatible APIs. The model never gets the final word on whether the work is correct. When something breaks, only the responsible agent is relaunched.

How the orchestrator works
Goal: "Build a pricing site with a checkout demo" │ ▼ Plan break goal into agents + a file contract │ ├─ work design system, copy, palette ├─ design mockups (HTML / CSS) ├─ code the working site + checkout └─ verifier reads it all, QA │ ▼ Quality gate broken link? dead import? missing file? → re-run owner │ ▼ /workspace your deliverable, on disk
Under the hood

One proxy holds the keys. The tools never see them.

A small server runs on your machine, routes every request to the right provider, and injects your context along the way. No Docker. No cloud.

Configure once

Chat, code, work, design, orchestration — five slots, one config. Add a key, every slot can use it.

Keys stay on your Mac

Your real keys are stored in an encrypted file (~/Library/Application Support/openaxis/secrets.enc, AES-256-GCM), load into memory, and route through a localhost-only proxy. The tools only ever see a local token.

Updates don't break it

The wrapped tools are cloned unmodified. Every customization lives in CSS and JS injection. Upstream updates land clean — no merge conflicts.

See the full architecture
Your keys, your machine

We don't ask for your trust. We prove it.

There's no OpenAxis server. There's nothing to sign up for. Everything runs and stays on your Mac.

No account, no cloud, no telemetry

OpenAxis has no backend. Your projects, memory, and chats live in your home folder. Nothing leaves without you telling it to.

Open source, end to end

MIT licensed. The proxy, the secret handling, the override layer, all auditable. If you don't trust it, read it.

Read how OpenAxis handles your data

Download it. Add your keys. Create.

Drag OpenAxis to your Applications folder, then add your API keys in the Config panel. Apple Silicon, macOS 14 and up.