Skip to main content
A session’s permission mode decides which tool calls the agent makes without asking. A call that needs permission appears in the thread as a prompt (see Approvals, questions and plans).
Answer to !mode plan, and a later turn whose footer shows the plan mode

Modes

These are Claude Code’s permission modes: Claude Code defines which calls each one lets through. Outside bypassPermissions, spawn_thread and post_thread ask for approval; read_thread never asks.
Not in the open-source code yet (model proxy, which makes Codex sessions work in the public build).
The Codex harness supports default and bypassPermissions only.

Default

A new session starts in bypassPermissions. To change that for sessions created from then on, set PERMISSION_MODE in the gateway’s environment (in one-machine mode, the process’s). See Configuration.
Not in the open-source code yet (runner isolation). Until it lands, sessions on one computer share a Unix user and can read each other’s files and secrets.

Changing a session’s mode

  • The mode survives a runner restart and idle exit.
  • Anyone whose messages are delivered to the session can change it (see Shared threads).
  • The turn footer and !status show the mode only when it is not bypassPermissions.