All documentation

Documentation Settings: Account

Account: what this Mac shares

Whether your phone and the web may run work here, how private new discussions are, GitHub for seats, phone pairing and previews, and resetting the app.

Mac only. These rows sit in Settings → Account → Account → Sign-in & Security, after Trusted devices. They decide what this Mac offers your other devices. The thirteen "Ask before…" switches in the same card are covered on the permission modes page.

Sharing this Mac with your other devices

SettingDefaultWhat it doesChange it when
Run requests from my other devicesOnYour phone and the web may start a discussion that runs here, with this Mac's seats and permission mode. Off, it still syncs but never picks one upThe Mac holds work you do not want started remotely
Show this Mac's seats on my other devicesOnWhen a discussion is set to run here, the phone and web show these seats. Only the choices travel, never a key, a command or an endpointYou would rather the seat list stayed on the Mac
Pull request switches from my other devicesOnThe phone and the web may turn on fixing, merge when ready and archiving for a discussion's pull requests here. Each goes through the same rules as the PR menu on this Mac. Off, a switch turned elsewhere waits until this is on againYou want those switches turned only in front of this Mac
Approve only on this MacOffA question a run here asks is answered here. The phone, web and Slack show it and say where to answerYou want every approval in front of the screen doing the work. A team can force it on
New discussionsSyncedSynced: on your account. Private live view: nothing stored on our servers, a paired phone can follow it end-to-end encrypted. Keep on this Mac: nothing leaves but what each seat sends its own AIYou work on code that must not leave the machine. A team can rule out the less private options
GitHub for seatsAsk meWhen a seat's gh command needs your GitHub sign-in: Ask me, Always allow or NeverYou connected the GitHub app (each run then has its own token), or never want your sign-in used

Private discussions do not use Our Keys or the Free Key, because those are reached through our servers. Each discussion can change its own level under ⋯ → Privacy.

Phones for private discussions

A paired iPhone can list, watch and write to this Mac's Private live view discussions. Messages are sealed with keys made on each device, so our servers carry them without being able to read them.

How to use it.

  1. Press Pair a phone. A code appears.
  2. On the iPhone: Settings → Account → Private discussions → Pair with a Mac, and scan it.
  3. Check the six digits match on both screens. Up to ten phones.

Preview on my phone

Off by default. When on, Background tasks offers to show a local app you are building on your phone: scan the code and it opens over your Wi-Fi with a one-time code. Nothing goes through our servers. A phone preview lasts 5, 15 (default), 30 minutes or an hour, and also ends after ten idle minutes or when the app quits. My own tunnel address takes the https address of a tunnel you run to this Mac, for use away from your Wi-Fi; the app shows it as a code and never connects to it. A team can turn previews off.

Mac: Settings → Account → Account → Sign-in & Security, the rows from Run requests from my other devices to New discussions
Mac: Settings → Account → Account → Sign-in & Security, the rows from Run requests from my other devices to New discussions

Reset the app, keep my work

A clean start when something is stuck. Reset… removes settings, seats, keys, models, this Mac's account sign-in, the Claude Code or Codex sign-ins added in the app, and the window's caches, then restarts. Every discussion, folder, memory, skill and automation stays, and so does the workspace. The terminal's own CLI sign-ins and the Keychain are not touched. You will need to re-enter provider keys afterwards.

See also

Not what you were looking for? The help centre answers one question at a time, and the support page says how to reach a person.