Access modes

Each runner profile has an access mode. It decides how much a run on that profile may do without asking you. Minga uses the CLIs’ own permission modes and sandboxes for this; it adds no wrapper of its own.

The three modes

Mode	Claude Code	Codex	When a prompt comes up
Auto (default)	Auto mode: its classifier reviews risky steps	workspace-write sandbox, approvals on request, and Codex’s own auto-review decides what needs more	Rarely. Codex’s reviewer answers most of them.
Ask	Default mode: edits and commands ask	read-only sandbox, approvals on request	Every edit and command becomes an Allow card in Needs you
Full	bypassPermissions	danger-full-access, never asks	Never. The CLI runs unrestricted, with full disk and network access.

Set it from the terminal:

minga profile set claude-personal access ask

or in the app under Settings › Runners, on the profile’s row, if you own the runner. The app asks you to confirm Full access.

Auto in detail

• Claude Code runs in its auto mode. If auto mode is not available for the model, the run switches to accepting edits on its own while commands still ask, and says so once in the transcript.
• Codex runs in its workspace-write sandbox with approvals on request, plus Codex’s own reviewer: exactly what Codex calls “Approve for me”. The reviewer approves or denies requests to leave the sandbox, network requests and MCP tool prompts. See Codex auto-review.
• Network is on for Codex in Auto, unless you turn it off (below) or the profile’s own config.toml says otherwise.
• Your MCP servers run without asking in Auto, unless your CLI config asks for a server or tool explicitly.

When to choose Ask

Choose Ask if you want to confirm every edit and command, for example on a profile that can reach production credentials. Runs wait while a card is open, so Ask is slower and needs you nearby. In Ask, Codex has no network.

Caution

The access mode, through the CLI’s own permission mode and sandbox, is what stands between a run and your git and gh logins. Minga does not refuse a push, force-push, merge or pull request close on its own. See Data and security.

Other profile settings

minga profile set <id> <key> <value>:

Key	Values	Default	What it does
access	auto, ask, full	auto	The access mode
mcp	cli, minga_only	cli	Which MCP servers a run loads: your CLI’s own plus Minga’s, or Minga’s only
mcp-approval	approve, ask	approve	In Auto: your MCP tools run without asking, or ask when the CLI asks (in Codex this also turns its reviewer off)
network	on, off	on	Codex in Auto only: whether commands can reach the network
model	a model id, or default	the CLI’s	The model for runs that name none
effort	low, medium, high, max, or default	the CLI’s	The effort for runs that name none

The command prints the profile’s effective settings after each change, and a running runner picks it up at once.

Advanced overrides

To set a CLI’s own permission mode or sandbox directly, regardless of the access mode:

minga profile cli codex-work --codex-sandbox workspace-write --codex-approval-policy on-request
minga profile cli claude-personal --claude-permission-mode acceptEdits
minga profile cli claude-personal --claude-sandbox on

unset hands a value back to the access mode. Without flags, minga profile cli <id> shows what a run passes. A profile with an override shows its mode as (custom). All values are in the CLI reference.

The profile is the ceiling

A run can only narrow what its profile allows, never widen it. Lea’s own turns, for example, plan and do not edit your repo, and by default load only Minga’s tools. Worker presets can narrow a worker to Minga’s tools too.