Persistent AI teammates,
organized by conversation,
on your own Mac.

Settings double as the setup wizard: one local folder as the shared workspace, plus at least one OpenAI-compatible endpoint. Each enabled model on an endpoint is its own row, with strengths, thinking levels and price; click a row to make it the default. From then on an agent picks the model and thinking level for each turn — and leaves a reason — instead of asking you every time.

The API key goes in this field only. Never in chat.

Name, duties and boundaries are all required. The avatar is generated from the name. On save, one more face appears on the roster row and a direct chat opens. The roster has no cap and does not include you.

The roster is the row of avatars at the top of the sidebar.

Tell Coordinator who you need. It uses built-in tools to create Researcher and Writer, opens the group "Research" and pulls all three in. Creating bots, groups and configuration is one sentence in a chat.

Bots can create bots, groups, endpoints and MCP servers.

Send a message without @ and every bot present decides to join or pass; passing never enters the transcript. An @mention makes joining mandatory. The app does not arbitrate who speaks and has no turn-count breaker. The one who joins has the model its turn runs on beside its name.

Judgement: Researcher joins, the others pass.

Researcher wants an MCP server to fetch web pages. Adding MCP, adding endpoints, reading or writing outside the workspace and outbound network all wait for you; adding MCP can never be set to Always allow. Calls to configured tools run directly. What waits on you is marked on the conversation in the sidebar; there is no separate notifications page.

Allow once or deny. Secrets never enter the transcript.

Researcher runs a script to check the figures; its output scrolls under that line while it runs, then folds to one line. Done, it writes @Writer into its message and Writer wakes up to continue. Files written during the turn attach to the reply automatically; there is no separate artifact store.

It folds to one line: command · exit code · how long.

Open report.md and the main column splits off a pane for it, in a tab named "Research's artifacts": the files this job touched on the left, a Monaco editor on the right with line numbers, find, folding, and Markdown switching between rendered and source. Edit and press ⌘S to write back to the same path. A conversation has one preview; opening another file turns it to that one.

It writes a real file on disk.

The conversation pane is narrow now, so its header actions fold into ⋯. Pick Trace and the job is drawn by who woke whom: a card per turn, with the files it handed over on the card. Under each Bot card is the model, thinking level and message kind its turn ran on, picked by an agent before the turn; click it for why, and how many hops it took. The review at the end of a correction lands here too, and only a verdict against the model becomes that Bot's experience.

The model each turn ran on, and why, sits on its card.

Right-click anywhere in a pane to split it up, down, left or right; the new empty pane offers New terminal, Workspace and Routines. Start a terminal and run pnpm dev: it is your own shell, it needs no approval, and no Bot can touch it. The current pane is framed in the accent colour; the layout is remembered on this Mac, and Quit and reopen brings back the split and the terminal.

Closing a terminal tab leaves it running; reattach from "+".

The window hides in the tray, and running turns and the pnpm dev in the terminal carry on. When Coordinator finishes its check, a macOS banner opens straight to that conversation, and the Dock badge counts only what you have not seen plus what is still waiting on you. Stop in a direct chat ends the current turn immediately; only Cmd+Q or Quit in the tray ends the window and the daemon.

Closing hides. It does not quit.

A paired phone reaches this Mac through a relay you deploy yourself: conversations, approvals, the workspace and your terminals are all there, encrypted end to end between the two, with the relay passing along ciphertext it cannot read. Ask @Writer for one more section from the phone and it is still the Writer on the Mac doing the work; read it on the phone and the Mac's Dock badge clears too. Pairing happens once: the Mac's settings hand out a one-time code, you paste it on the phone, check that the fingerprints match, and approve at the Mac. It is an experimental feature, off by default, and a release build cannot pair yet.

Your own relay serves the page; messages are end-to-end encrypted.