> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opencomputer.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Permission modes

> New sessions start in `bypassPermissions`, where nothing asks for approval; `!mode` changes one session and `PERMISSION_MODE` all new ones

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](https://docs.opencomputer.dev/slack/approvals-questions-plans.md)).

![Answer to !mode plan, and a later turn whose footer shows the plan mode](https://mintcdn.com/opensandbox/wc3ROkMcBR7DifaQ/images/slack/mode.png?fit=max\&auto=format\&n=wc3ROkMcBR7DifaQ\&q=85\&s=fb53e707233723027876f510641a5799)

## Modes

| Mode | `!mode` argument | Behaviour |
| - | - | - |
| `bypassPermissions` | `bypass`, `yolo` | Nothing asks for approval. The default. |
| `default` | `default`, `ask` | Tool calls that need permission ask first. |
| `acceptEdits` | `accept`, `acceptedits`, `edits` | File edits run without asking; other tool calls that need permission ask. |
| `plan` | `plan` | The agent investigates and presents a plan for review before changing anything. |
| `auto` | `auto` | Claude Code's auto mode: the harness decides per call whether to ask. |

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.

> [!NOTE]
>
> 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.

> [!NOTE]
>
> 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

```text theme={null}
!mode plan
```

| Set by | Mode |
| - | - |
| `!mode <argument>` | The named mode. Applies at once, including to a running turn. |
| "Approve · auto-accept edits" on a plan | `acceptEdits` |
| `spawn_thread` | The new session starts in its parent'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](https://docs.opencomputer.dev/slack/shared-threads.md#who-can-steer)).
* The turn footer and `!status` show the mode only when it is not `bypassPermissions`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.