Skip to main content
Version: 1.7.0

Agent Permissions

Direct Agents tab showing connected provider summaries and unavailable providers

Configure permissions for agents launched directly from RepoPrompt and the separate policy for sub-agents launched through MCP. Sub-agent policy can use Safe Managed behavior, inherit direct-agent settings, or use custom settings.

Open Settings → Agent Mode → Agent Permissions. The page has two tabs with separate responsibilities: Direct Agents and Sub-Agents. Model selection remains in Agent Models.

Direct Agents and Sub-Agents tab selector

Direct Agents​

This tab configures provider-native permissions for agents you launch directly from RepoPrompt. Expand a connected provider row to change its permission level and, where supported, Tools & Runtime Options.

Connection indicators and summary values describe your current setup. A green indicator means the provider is available; it does not mean it has unrestricted access.

Codex CLI​

Codex CLI direct-agent sandbox and third-party MCP summary

The row summarizes the sandbox and third-party MCP policy. Expand it for Codex permission levels and runtime tool controls. Third-party MCP servers are controlled individually and are off by default; that control is separate from the RepoPrompt MCP tool list.

Claude Code​

Claude Code direct-agent permission mode and third-party MCP summary

The summary shows the selected Claude permission mode and MCP scope. Expand it to configure Claude's provider permissions and tool/runtime settings. Auto-approve Edits and RepoPrompt only are the selections pictured, not a recommendation to enable broader access.

OpenCode and Google Antigravity​

OpenCode direct-agent ACP session mode and MCP support summary

Google Antigravity direct-agent ACP mode and MCP management summary

These rows expose each provider's ACP session mode. The provider's capabilities determine which permission and tool controls are available. The screenshot reports no third-party MCP support for OpenCode and provider-managed MCP for Antigravity; do not assume the same MCP controls apply to both.

Disconnected providers​

Disconnected Cursor CLI, Grok Build, and Devin CLI rows and Open CLI Providers button

Unavailable providers are listed under Not connected and cannot be expanded for editing. Open CLI Providers opens connection setup. A provider moves into the connected list when it becomes available.

Sub-Agents​

View the complete Sub-Agents tab

Agent Permissions Sub-Agents tab showing policy selection, Safe Managed preview, effective profiles, and related settings

Sub-agent sandbox policy selector with Safe Managed, Inherit Provider, and Custom

This policy applies when another agent launches a sub-agent through MCP:

PolicyBehavior
Safe ManagedApplies RepoPrompt's managed provider profiles instead of the direct-agent settings.
Inherit ProviderUses the direct-agent provider settings, including permissive modes you enabled there.
CustomUses independent per-provider sub-agent permission levels.

Custom mode exposes Per-provider sub-agent modes. These affect future sub-agent launches without changing Direct Agents settings. Inherit Provider can pass through Full Access; review direct-agent settings before choosing it.

Preview Safe Managed profile​

Expanded Safe Managed policy preview

The preview explains the policy and shows an effective profile for each available provider.

Safe Managed disables Claude Bash, forces Claude to strict MCP, and suppresses user-enabled third-party MCP servers for Codex. Codex Bash remains enabled under its managed Auto Review workspace sandbox.

Grok Build uses its Default mode for MCP launches. Its own rules, including inherited Claude Code permission rules, can allow requests without asking RepoPrompt. Safe Managed therefore does not guarantee an approval prompt for every provider action.

Effective per-provider profile​

Safe Managed profiles for connected providers and unavailable-provider indicators

Read these summaries for the connected providers. They show the resulting sandbox or permission mode and third-party MCP handling. The rows are a preview of policy, not a second set of editable Direct Agents settings.

Overseer​

Overseer full access switch and explanation of its session-wide permissions

Overseer full access (no approvals) grants an Overseer access to every session without approval or confirmation cards. It can observe, organize, control, restructure, spawn, manage worktrees, retire, and delete sessions. The switch is off by default and appears on both permission tabs.

Review its access in Active delegations. Turn the switch off to revoke this standing access immediately. This is a separate, app-wide grant; the Direct Agents and Sub-Agents settings above do not limit it. Only you can change this switch in the UI; it is not exposed through the MCP App Settings tool.

Links to CLI Providers, Workspace Approvals, MCP Tools, Agent Models, and Agent Mode Overview

Both tabs share secure-permission storage diagnostics. If a degraded-storage banner appears, check it before assuming a permission change was saved; failed writes can return to the effective stored value.