ACP coding agents

An ACP agent connects a program implementing the Agent Client Protocol to AI Chat. The program runs on your Mac in the agent's folder, uses its own account and tools, and sends its messages, plans, changes and permission requests back to Redcast.

Set up an agentCopy Anchor Link

1. Install and sign in to the coding agent using its own setup.
2. Create a Redcast agent and choose its working folder.
3. In Runs on, select the matching preset or specify an ACP command.
4. Check its command and arguments, then open an AI Chat with this agent.
5. Send a small read-only request and verify its model and permission controls.

The current presets use these commands:

The editor lets you change the executable and arguments. The first npx start may download its adapter and take longer. A custom executable must speak ACP over standard input/output; an ordinary interactive terminal command is not enough.

Model, reasoning and modeCopy Anchor Link

Chat Settings displays the options reported by the agent: model, reasoning, mode and any other selects it supports. Redcast does not invent choices for an agent that supplies none.

Changing a choice affects the current chat and becomes the agent's default for new sessions. Other existing chats keep their own choices, including across an idle stop or relaunch. Options no longer offered by an agent may be ignored or removed from its saved defaults.

Available slash commands come from the active session. Type / to see them; a fully typed command is sent as that command. Redcast does not manufacture a universal slash-command list.

Tools and permissionsCopy Anchor Link

ACP agents use their own tool loop and file access. Redcast displays their permission requests and tool results, including supported diffs and output. The native Files and Terminal tool families are not injected as a second set of ACP tools.

The agent's own operating-system access and configuration still apply. Read each request before allowing it. In unattended runs, background permission rules determine whether Redcast can show a question or must decline it.

Sessions and idle behaviorCopy Anchor Link

Each chat gets its own agent session. Redcast saves the session identity and tries to load it on the next turn; if the agent cannot restore it, a new session is started with the available briefing.

An idle agent process stops after two minutes. An unattended agent is released when its run ends unless a chat still needs it. A new empty chat displaying the agent does not start the process until needed.

These sessions also appear in Agent Sessions as Redcast chats, avoiding duplicate entries for the same underlying session.

Choosing between routesCopy Anchor Link

Use an installed chat provider for simple model conversation through an existing CLI. Use ACP when you need that agent's tools, permissions and project session. Use a native Redcast agent when you want Redcast's tool loop on an API model. The Codex (ChatGPT) API connection is a fourth route and does not launch the Codex CLI.