Claude Code permissions: modes, approvals and a safe setup

By Arun Dass · Published 3 October 2026 · Updated 2 November 2026

Anyone who runs a coding agent decides what it may do without asking. Claude Code has permission modes for that: plan mode reads and proposes, the default mode asks before edits and commands, and auto mode skips most asking. Friday runs your own Claude Code, with its own settings, on your computer.

What are the permission modes?

ModeWhat the agent may doUse it when
PlanRead the code and propose a plan. It does not edit your source until you approve the planYou want to agree the approach before any file changes
DefaultEdits and commands ask firstEveryday work where you want to approve each step
AutoRuns with fewer stops. In Claude Code a classifier still checks each actionA task you trust, in a folder you can reset

Codex has its own approval settings, and the same word can mean different things in each. Codex’s Auto still asks before network access or edits outside the workspace, and its never approval policy is the nearest match to running with no asking.

Who approves a command?

You do. Friday runs on your own computer, under your own login, so when a tool asks before running something, the question comes to you before the command runs. Several people can share a repository without sharing a session: agree the rules in the repository, in a CLAUDE.md or AGENTS.md, and keep personal settings in your own configuration.

How should you set it up?

  1. Start new work in plan mode, and read the plan.
  2. Move to the default mode to make changes. Approve commands one at a time and read what each one does.
  3. Use auto only for a bounded task in a folder you can reset, ideally in its own git worktree.
  4. After the run, read the change set, and leave notes on any line before you keep it.

What changes when several agents run at once?

Each agent has its own mode, so one can be read-only while another edits. Friday runs 16 coding tools by name plus any ACP agent on your own plans, and each agent can work in its own git worktree, so a risky run touches a copy and not your main folder.

Crew teammates, the AI teammates in the app, have a per-teammate access level: Read only, Ask before changes or Full access. You can Stop all and Pause.

Friday reviews each run’s changes line by line, with notes sent back to the agent, and git is built in. The permissions themselves stay with each tool.

Sources

Checked against each maker’s documentation on 13 October 2026. These tools change often, so check the latest version.

Common questions

Does Friday change what Claude Code is allowed to do?

No. Friday runs your own Claude Code on your computer, so Claude Code’s own settings still apply.

Can I see what an agent did?

Yes. Each run ends in a change set you review line by line before you keep it.

Can a teammate approve a command in my session?

No. The free app runs on your computer for one person. Friday Team is the hosted version for several people in one session, by arrangement: contact us.

Run your next task in Friday.

Free and open source (MIT), on your own computer: the desktop app for macOS, Windows and Linux, or one command with Node.js 22.