napdock Download
napdock Changelog FAQ

What leaves your Mac.

On This Mac only, nothing goes to us. This page says exactly what does when you sign in, what your agents send their own providers, and how the app keeps each part in its lane.

This website

It sets no cookies, runs no analytics and has no forms. The one thing it keeps, in your own browser, is whether you chose light or dark.

On your Mac

With Where sessions live set to This Mac only, sessions run in the executor on your Mac and their history stays there. Nothing is uploaded to napdock, nothing is checkpointed, and you need no account. Your repositories and worktrees are ordinary folders you own; the app never deletes your work.

With an account

Cloud sessions are stored in your account so they can sync, be checkpointed and move between machines. That means:

Your identity
Your passkey or Google sign-in, and a device key that stays on your Mac
Projects and sessions
Their names, settings and the public conversation
Checkpoints
The files of each checkpoint, content-addressed and compressed
Never stored
Your providers' logins and their private reasoning

Only one machine can write to a session at a time, and a machine that gives a session up is fenced so it cannot write again. Destructive steps in the CLI need an explicit --confirm.

Your providers

Claude Code, Codex and Pi talk to their own services on your own login, exactly as they do in a terminal. What an agent sends its provider, such as your prompts and the files it reads, is covered by that provider's terms, not ours.

Credentials

Each provider's CLI keeps its own login, and napdock never reads or copies it. Secrets the app holds itself, such as MCP plugin tokens, your GitHub accounts and the CLI's session, are kept in the macOS Keychain. MCP servers sign in with OAuth in your browser, so the app never sees a password.

Sandboxing

Helper programs and terminals the executor starts run under the macOS sandbox. An extension's interface runs in a sandboxed worker, and its main part gets only the network, file and process access it declares, which you can revoke in Settings.

Agents follow their permission mode. In Supervised, every command and edit waits for Allow once or Deny. In Full access an agent is not confined, so keep that mode for work you trust.

Telemetry

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