Permission modes
Claude Code has four permission modes for tool use. kanade surfaces them as a single chip in the input bar so you don’t have to remember the Shift+Tab dance.
The four modes
Section titled “The four modes”| Mode | Behavior |
|---|---|
default | Claude asks before running write-side tools (Edit, Write, Bash). |
accept-edits | Edits + writes go through without asking. Shell commands still ask. |
plan | Plan mode — Claude can read but cannot edit, write, or run shell commands. Used for design discussions. |
bypass | All tools run without asking. Use only in environments you trust. |
How the chip works
Section titled “How the chip works”Click the chip in the input bar to cycle: default → accept-edits → plan → bypass → default. Each click injects ESC [ Z (Shift+Tab) into the PTY — the same
keystroke Claude Code already listens for — so Claude Code’s internal mode state
stays in sync with what the chip displays.
A small reset (↺) sits next to the chip. If the chip ever drifts out of sync
(network glitch, manual mode change in the terminal), reset re-syncs to default · ask without injecting anything.
The bypass confirm
Section titled “The bypass confirm”Bypass is loud on purpose. Clicking the chip to advance into bypass opens a modal explaining that Claude can run any tool — file edits, shell commands, network requests — without asking. You confirm explicitly before the mode engages.
Persistence
Section titled “Persistence”The mode you end on is per-account, not global. It writes to
~/.claude/settings.json :: permissions.defaultMode and applies the next time
that lane spawns a session. The other lanes keep their own defaults.
Set a different default through the Setup tab in the right rail — that edits the same key but does it without injecting into a live PTY.