Skills Reference
ACP
What it does
Sets up, authenticates, and runs external coding tools such as Claude Code, Codex, and Gemini CLI through the Agent Client Protocol, so your assistant can hand development tasks to them.
Setup required
The protocol adapter is installed automatically the first time you use an agent. For Claude Code that is everything: sign-in runs through an in-app Connect card, so there is nothing to install yourself. Codex additionally needs the Codex CLI (version 0.111 or higher) already on your PATH, since its adapter calls that CLI and inherits its sign-in. Say “Set up ACP” to walk through it.
Permissions
- Host shell access for spawning external processes
Common prompts
| You say... | What happens |
|---|---|
| “Use Claude Code to fix the bug in server.ts” | Delegates to Claude Code agent |
| “Ask Codex to refactor this module” | Delegates to Codex |
| “Check on my coding agent” | Gets agent status |
| “Cancel the coding agent” | Aborts the agent |
Configuration
- Supports multiple external development tools (Claude Code, Codex, Gemini CLI)
- Agents run as separate processes with their own context
- Status tracking: pending, running, completed, failed, aborted
Tips & gotchas
- Fully independent. ACP agents are separate processes with their own context window and tools.
- Self-contained tasks. Best for tasks like fixing a bug, refactoring a file, or writing tests.
- Coordinated results. Your assistant coordinates with the agent and reports back results.
- Choose the right agent. Claude Code for general development, Codex for code generation, Gemini CLI for Google ecosystem integration.