Skip to main content
Version: 1.7.0

Overview

Overview model links, supervision, provider status, usage display, and cleanup controls

Configure Agent Mode behavior and find the settings for models, providers, permissions, and context building.

Open Settings → Agent Mode → Overview. This page combines shortcuts to detailed configuration with a few app-wide behavior controls. Screenshots illustrate the controls; the selections shown are examples rather than recommended defaults.

Models and context​

  • Oracle Model opens Agent Models. Oracle analyzes the current file selection and chat history for planning and review, without tools or file edits. Change its model on the linked page.
  • Context Builder Agent also opens Agent Models. Choose the agent and model that explore the repository and gather relevant files for Oracle.
  • Sub-Agent Role Defaults opens Agent Models. Assign models to orchestration roles: Pair for primary work, Design for interface and copy work, Explore for investigation, and Engineer for implementation.

The model names shown on Overview summarize your configuration. They are navigation links, not model pickers.

Sub-Agent Supervision​

Sub-Agent Supervision panel with the default wait menu and its explanation

Default subagent wait sets how long an orchestrating agent normally waits for a sub-agent before checking back. The available intervals are 2, 5, 10, 20, 30, and 60 minutes.

Shorter waits allow more frequent progress checks; longer waits reduce routine model calls. Completion, questions, or your steering can end a wait early. An agent can request a different wait for an individual task, so this is a default supervision interval rather than a task time limit.

CLI Providers​

CLI Providers summary with provider connection indicators

Open CLI Providers to connect runtimes, manage authentication, test connections, and configure provider controls. Overview summarizes the connection state for Codex CLI, Claude Code, OpenCode, Cursor CLI, Grok Build, Google Antigravity, and Devin CLI.

These indicators summarize the connection information already held by the app. Use Test Connection on the provider page to check availability again.

Usage Limits​

Usage Limits switch and link to provider usage sources

Show usage limits when available displays provider plan usage in Settings and a compact indicator in Agent Mode. Enable each usage source in CLI Providers. This display is read-only: it does not choose models or enable usage balancing. Configure routing separately in Agent Decisions.

Provider Conversation Cleanup​

Provider Conversation Cleanup panel with Archive and Delete choices

Cleanup action controls what RepoPrompt requests from a supported provider when you delete an Agent Mode session:

  • Archive requests archiving of the provider conversation.
  • Delete requests deletion of the provider conversation.

Local session cleanup continues if the provider does not support conversation cleanup. Selecting an action does not immediately archive or delete existing sessions.

Provider-side cleanup

Deleting an Agent Mode session can also affect its provider conversation. Choose the cleanup action before removing sessions; support for the requested action depends on the provider.

Provider environment filtering (opt-in)​

Environment variable withholding list, provider-specific exceptions, Apply, and Reload

Use this section to withhold selected ambient environment variables from newly launched provider processes. Leave both lists empty to preserve the existing authentication and toolchain environment.

  1. Enter variable names in Withhold ambient names for all providers, separated by commas or spaces. Names are exact and case-sensitive; do not enter values or wildcards.
  2. Choose a provider under Pass-through exceptions for and enter any withheld names that provider still needs.
  3. Choose Apply to save. Reload discards the draft and reads the saved lists again. Apply or reload an edited exception list before switching providers.

Filtering applies to new provider processes, including probes and headless launches. It does not alter running sessions or interactive user terminals, and intentional app/runtime overrides remain available. Withholding a required variable can break authentication or tools; add a provider exception when needed.

This is a partial mitigation. It does not restrict credential files, shell profiles, installation or provisioning identity checks, or other capabilities available to the same user. If the lists change elsewhere while you edit, reload them before applying.

Require Codex project-hook approval​

Codex project-hook approval switch and workspace override menu

The app-wide Require Codex project-hook approval switch determines whether Codex may begin without approval of the displayed project hooks.

When approval is required, Continue Without Hooks is unavailable. The first Codex turn remains blocked until those hooks are approved or become trusted externally. Turning off the requirement permits the continue-without-hooks path; it does not itself approve or trust hooks.

When a workspace is available, In this workspace can override the app-wide setting:

  • App default follows the app-wide switch.
  • Always require approval requires hook approval in this workspace.
  • Don't require approval allows this workspace to use the continue-without-hooks path.

Handoff Instructions​

Handoff Instructions editor, character count, Save, and Clear Saved Instructions controls

Enter reusable instructions that the titlebar’s Handoff action appends to a handoff. The saved text applies across the app.

  • The editor accepts up to 20,000 characters and displays a character count.
  • Save stores a changed, valid draft. Text that exceeds the limit must be shortened before saving.
  • Clear Saved Instructions removes the saved text and clears the editor.

For example, you could save:

Summarize the task, decisions, changed files, and validation results.
List the remaining work and any unresolved questions.
Saving and concurrent changes

If the saved instructions change elsewhere while you have an edited draft, the page warns that saving will replace the newer value. If global settings cannot be saved, a separate warning explains that changes are active only for the current launch until persistence is restored.

Agent Permissions​

Agent Permissions links for direct agents and sub-agents

These links open Agent Permissions:

  • Direct Agents configures provider controls for agents you launch directly, such as Claude Bash access, Codex sandbox permissions, ACP session modes, and MCP restrictions.
  • Sub-Agents configures the policy for agents launched through MCP. The displayed policy name summarizes the current setting. Safe Managed applies managed overrides; other policy choices are configured on the linked page.
Two permission scopes

Direct-agent controls and sub-agent policy are separate. Changing a provider control does not mean every MCP-launched sub-agent will use that same setting.

Context Builder Budgets & Timeouts​

Context Builder Budgets and Timeouts settings link

Context Builder Budgets & Timeouts opens Context Builder, which owns token budgets, prompt enhancement, question timeouts, and clarifying-question behavior.

Agent Workflows​

Agent Workflows settings link and cleanup guidance summary

Open Agent Workflows to manage built-in workflow visibility, featured workflows, custom Markdown workflows, and cleanup guidance. Overview displays a summary; change the workflow options on their own page.

Agent Chats​

Agent Chats panel with Show chats created by MCP tools switch

Show chats created by MCP tools controls whether the chat list includes Compose tabs created through MCP before an agent has run in them.

Enable it to inspect and adjust those tabs’ selections, prompts, and Context Builder runs in Compose. Disable it to omit those not-yet-run chats from this view. The switch changes visibility; it does not delete the chats.