Questions, answered.

A native Mac app for running coding agents. Claude Code, Codex and Pi work side by side in one window, each on its own login, with one approvals card, one sidebar of sessions and a Git worktree for each session. You hear from them when a turn needs you.

No. Set Settings → Worktrees → Where sessions live to This Mac only and nothing is uploaded: sessions, worktrees and history stay on your Mac. Signing in to a napdock account adds the cloud: checkpoints, sync, cloud containers and moving a session between them and your Mac. The hosted service is not open yet.

Claude Code through Anthropic's Claude Agent SDK, Codex through codex app-server, and Pi through its RPC mode. Claude offers Sonnet 5.5, Opus 5.5, Fable 5.1 and Haiku 5.5, or any model id your account can use. Codex offers GPT-6.1 Sol, GPT-6 Astra, Sol and Luna, and GPT-5.6 Sol, Terra and Luna. Pi uses whatever models your Pi is set up with.

You need at least one, signed in through its own CLI the way you use it today. napdock never asks for, reads or copies those logins, and it shows which providers are ready before you start a session.

Yours. Each agent talks to its own provider on your own subscription or key, exactly as it does in a terminal. For Claude and Codex the status bar shows how much of your plan's limit is left.

Macs with Apple silicon (M1 or later) on macOS 13 Ventura or later. There is no Intel, Windows or Linux build.

There is no public download yet, and no pricing has been set. When it ships it will be one Developer ID signed and notarized app. Your model usage is always billed by your provider, not by us.

Only if you let it. There are four permission modes: Supervised, where every command and edit waits for Allow once or Deny; Auto-accept edits; Auto; and Full access. You can change the mode for each session at any time.

An approval covers one action. If you want an agent to stop asking, raise the session's permission mode, so the choice is visible in one place instead of hidden in a list of past answers.

Yes. Change the provider in the composer and the next agent continues the same session, with the conversation so far handed over as text. The transcript marks where it happened.

Work modes for one message. Plan asks the agent for a plan before it edits anything, and Review asks it to review the changes instead of making new ones. After that message the session goes back to normal. /plan and /review do the same from the composer.

A quick question asked on the side, with /btw or the side chats pane. It gets a read-only copy of the conversation, answers, and stays out of the main session's history.

Yes, in three ways. Each session can have its own Git worktree under ~/.napdock/worktrees, so two agents never edit the same checkout. Claude's subagents are listed live in their own pane. And an agent can delegate tasks to new sessions: up to eight at once, never with more permission than the session that started them.

Yes. Fork the whole session, or fork from any finished turn to continue the conversation as it stood when that turn ended, in a new session.

Yes. Messages you send during a turn wait in a queue and go out in order. /stop ends the running turn, and drafts you have not sent are kept.

Yes: up to 10 files per message, 10 MB each and 16 MB in all. Images from the iPhone camera (HEIC) are converted on the way in. Attachments are read on your Mac.

The sidebar groups sessions into Needs input, Working and Recent, and the app can notify you when a turn finishes. A context meter shows how full each conversation is.

Sessions that live in the cloud: synced between your clients, checkpointed after every turn that changes files, and able to run in a cloud container and move back to your Mac. It also adds GitHub import, previews of a running port, browser terminals and the napdock CLI.

With a passkey or Google. The app opens your browser, shows a code to match, and keeps its device key on your Mac. Eight recovery codes get you back in if you lose your passkey.

The files and the conversation saved together when a turn changes files. Checkpoints are labelled by why they were saved and listed in the Checkpoints panel, where you can compare from any of them or browse the files as they were.

Only one machine can write to a session at a time. A move finishes or stops the running turn, saves a checkpoint, fences the old machine so it can no longer write, and restores the session where it is going. If both sides changed files, a handover view compares Yours and Incoming and lets you keep both, merge with AI or open a pull request.

No. In This Mac only, sessions run in the executor on your Mac and nothing is checkpointed or synced. Your agents still talk to their own providers, as they would in a terminal.

Not in This Mac only mode: your code stays on your Mac, and only your agents' providers see what the agents send them. With a cloud session, the files in its checkpoints are stored in your account so they can be compared, synced and restored.

Each provider's CLI keeps its own login, which napdock never reads. Secrets napdock holds itself, such as MCP plugin tokens and your GitHub accounts, are kept in the macOS Keychain.

napdock sends no analytics. It also starts Claude with its non-essential traffic switched off and Pi with its telemetry off. This website sets no cookies and runs no analytics.

Helper programs and terminals run under the macOS sandbox, and extensions only get the network, file and process access they declare. Agents themselves follow their permission mode: in Full access they are not confined, so keep that for work you trust.

Yes. There are 18 theme families with a light and a dark variant each, and you can import Zed themes. Interface and code fonts each have a bundled choice of families, and interface, prose and code sizes are set separately, from 10 to 24 points.

Yes. MCP servers that need a login sign in with OAuth in your browser, and their tokens are kept in the Keychain. You can use several GitHub accounts side by side.

Add panels, commands, keyboard shortcuts, settings pages, menus, status bar and composer slots, renderers for tool calls, files and Markdown, link handlers, themes, and tools, skills and hooks for your agents. Extensions are TypeScript; the app draws their UI natively.

Yes. ⌘K or ⌘⇧P opens the command palette, ⌘T starts a session, ⌘L focuses the composer and ⌘↩ sends. ⌃` opens the console. The features page lists every shortcut.

The interface is Rust on GPUI, drawn with Metal. There is no Electron and no web view, and an idle window draws no frames, so a dock of agents waiting on you uses next to nothing.

Markdown with tables and task lists, syntax-highlighted code, Mermaid diagrams you can zoom, math as Unicode, and diffs in unified or side-by-side view, including image, audio and video diffs.

No, it runs them. Each keeps its own login, model, tools and rules; napdock adds the window around them.