Two of these are built into OpenAxis: the chat and the orchestrator. Three are mature open-source tools, OpenCode, Open Design, and OpenWork, wrapped without touching a line of their source. Whichever you open, it uses the same API keys, the same theme, the same memory, and the same project context.
Talk to any model, without opening a second app.
A full chat built into the sidebar. Switch models mid-conversation, attach images and files, turn on web search when you need fresh facts, and pull a project's instructions into the thread. Every conversation is saved and backed up to disk.
One goal goes in. A team of agents runs with it. Out comes a folder of real files.
The orchestrator is an interactive assistant. You type what you need in plain language — "a pricing site with a checkout demo," "a Python library with tests," "a market research report" — and it plans the work as a visual DAG you can inspect. Each agent has a role: research, write content, design mockups, code, verify quality. They execute in dependency order and write real files to disk. A real deliverable, not a chat transcript.
Then a deterministic quality gate kicks in — plain code, no model. It statically checks the output for broken imports, missing files, dead asset links, unstyled pages, and APIs that don't line up between two agents' files. Defects force a fail no matter what the verifier model claims. Only the agent that owns the broken file gets relaunched.
A terminal-grade coding agent, in its own sandboxed view.
OpenCode is a serious code agent. It reads and writes files across your project and runs commands to get the job done. Inside OpenAxis it runs as a local server in a sandboxed view, themed to match the rest of the app, configured by the same proxy as everything else.
It's also the engine underneath. All three integrated tools drive OpenCode. That's why one config file can set them all up at once.
Generate and refine visual mockups, no terminal in sight.
Open Design produces interface mockups in HTML, CSS, and SVG and refines them across iterations. Normally it runs as a command-line daemon. OpenAxis launches it for you, captures it, and puts it behind a graphical view, so a designer who never opens a terminal can use it like any other app.
In an orchestration, the design agent receives the design system from the work agent and turns it into faithful mockups, which the code agent then reproduces.
Structured work and documents, tied to your projects.
OpenWork handles the structured side of building: content, documents, and organized work that isn't code or pixels. In OpenAxis it shares the same projects as everything else, so the instructions and context you set once follow you into Work and back out again.
In an orchestration it runs as the content engine, and it owns the design system: palette, typography, and the look the designer and coder then have to honor.
Stop re-explaining who you are and what you're building.
Memory is a profile plus a set of short, tagged facts *(under maintenance — coming soon)*. The profile describes you, your role, your stack, your preferences. The facts are reusable details. On each request, only the facts relevant to what you're asking get injected, inside a token budget, so the prompt stays lean instead of dragging your whole history along.
You stay in control. A global switch turns memory off entirely, and any single project can opt out on its own.
A project bundles instructions, a type, a preferred model, and context. It's how one setup reaches every tool.
Tied to a single tool: Code, Design, or Work. Open the tool and the project's instructions are injected into the AI context. A standalone project can also become a building block inside an orchestration.
These don't run alone, they coordinate several agents. They define the overall goal, the agents to chain together, and settings like auto-distribution, consistency checking, and retry-on-error.
Drag OpenAxis to your Applications folder, then add your API keys in the Config panel. Apple Silicon, macOS 14 and up.