The Mac app

Three layers, all on your Mac.

The window you click in can't start processes on its own: a separate host process does that, and only the CLIs talk to the AI providers.

Your Mac

  1. 01 The window

    What you click in

    Can't start processes on its own.

    • No Node.js access
    • No general-purpose shell bridge
    • A small, typed bridge to the app
  2. 02 The host

    Runs your terminals

    Starts and owns every terminal.

    • Owns the local database
    • Checks capacity before every start
    • Holds the emergency lock
  3. 03 The CLIs

    Talk to the providers

    Claude Code, Codex, Grok Build

    Each account signs in through its own CLI.

    • Real terminals, native interfaces
    • A private profile for each account

Leaves your Mac

  • Each CLI connects straight to its own provider: Anthropic, OpenAI or xAI.
  • Miko for iPhone, once you pair it, reaches your Mac through Miko's service.
  • If you turn them on, the DeepSeek research assistant sends project source to DeepSeek, and GitHub actions push to GitHub.

The Mac app in detail

The fine print, up front.

How the Mac app handles accounts, processes and data. Open any line for the specifics.

Accounts and sign-in

IsolationA private profile for every account.

A private CODEX_HOME per Codex terminal, and CLAUDE_CONFIG_DIR or GROK_HOME per account. This keeps accounts apart. It is not a file sandbox: terminals in the same workspace share its folder.

Sign-inEach account signs in once, through its own CLI.

Codex terminals receive short-lived access tokens from their account in memory, and Miko never saves them. Login links and device codes are never written to Miko's records.

Existing loginsMiko never imports the logins already on your Mac.

Each connection signs in fresh. Miko never reads or imports the Claude, Codex or Grok credentials already on your Mac, and the CLIs it starts don't inherit provider API keys from your environment.

Usage readingsNo prompts sent, no typing into your terminals.

Claude usage is read in a separate, short-lived terminal with customizations off. Grok uses its read-only billing call.

Stop, pause, recover

Emergency stopOne button halts everything until you unlock it.

Every runtime stops, Claude and Grok terminals included, and a lock is written to disk, so nothing restarts, even after a relaunch.

PauseNew work waits. Current work finishes.

A paused project admits no new work while what is already running finishes. Your own typing still goes through.

Background runtimeQuitting the window leaves terminals running.

Terminals belong to a background runtime, not the window. Reopening Miko reconnects to them. Emergency stop is how you halt everything.

RecoveryOpen conversations come back after a crash.

Account, workspace and conversation IDs are saved for this. When it isn't certain which process belongs to what, Miko holds it back for review instead of guessing.

What Miko keeps

Local stateKept in a local database on your Mac.

Projects, terminals and app state live in a local SQLite database. Every event and command receipt commits in one transaction.

Result previewsKept in memory, never saved as another transcript.

Claude shows the terminal excerpt captured when it notified you. Codex replies are read through the read-only conversation inspector.

Handoffs and teamsA manual handoff is only sent when you press Send.

In Miko mode, Miko messages the workers it supervises. Saved teams keep account IDs, providers and counts on this Mac, and a team with a missing account is refused rather than started smaller.

The app and your phone

The window itselfNo pop-ups, outside pages or web permissions.

Miko's window denies web permission requests, pop-ups and navigation away from the app. Saved records go through a second pass that removes tokens and keys.

Codex runtimePrivate copies, checked by version and hash.

Codex runs from app-private runtimes, checked before use: 0.154.0 for sign-in and Astra sessions, built from reviewed source, and 0.159.3 for ordinary terminals. A global upgrade can't change what runs.

Miko for iPhoneOff until you pair it, in Settings › Devices.

You pair Miko for iPhone from the Mac app or the web app, in Settings › Devices › Add iPhone, and you can remove a paired device at any time. A paired phone can start and stop terminals and answer agents.

Run more agents without losing control.

Join the waitlist and we'll email you an invite.

Starter regular price $29 $14.50 first monthCloud from regular price $79 $39.50 first monthLaunch offer: first month at half price, then the regular price. Not on 64 GB.