Skip to main content

ACP Providers

goose supports Agent Client Protocol (ACP) agents as providers. ACP is a standard protocol for communicating with coding agents, and there's a growing registry of agents that implement it.

ACP providers pass goose extensions through to the agent as MCP servers, so the agent can call your extensions directly.

Limitations
  • No session fork or resume: You can start new sessions, but goose session resume and goose session fork are not supported yet.
  • ACP session ID differs from goose session ID: Telemetry fields may not correlate across the two.

Available ACP Providers

Claude ACP

Wraps claude-agent-acp, an ACP adapter for Anthropic's Claude Code. Uses the same Claude subscription as the claude-code CLI provider.

Requirements:

  • Node.js and npm
  • Active Claude Code subscription
  • Authenticated with your Anthropic account (claude CLI working)

Codex ACP

Wraps codex-acp, an ACP adapter for OpenAI's Codex. Uses the same ChatGPT subscription as the codex CLI provider. Codex's sandbox blocks network by default — goose automatically enables network access when HTTP MCP servers are configured.

Requirements:

  • Node.js and npm
  • Active ChatGPT Plus/Pro subscription or OpenAI API credits
  • Authenticated with your OpenAI account (codex CLI working)

Setup Instructions

Claude ACP

  1. Install the ACP adapter

    npm install -g @zed-industries/claude-agent-acp
  2. Authenticate with Claude

    Ensure your Claude CLI is authenticated and working

  3. Configure goose

    Set the provider environment variable:

    export GOOSE_PROVIDER=claude-acp

    Or configure through the goose CLI using goose configure:

    ┌   goose-configure

    ◇ What would you like to configure?
    │ Configure Providers

    ◇ Which model provider should we use?
    │ Claude Code

    ◇ Model fetch complete

    ◇ Enter a model from that provider:
    │ default

Codex ACP

  1. Install the ACP adapter

    npm install -g @zed-industries/codex-acp
  2. Authenticate with OpenAI

    Run codex and follow the authentication prompts. You can use your ChatGPT account or API key.

  3. Configure goose

    Set the provider environment variable:

    export GOOSE_PROVIDER=codex-acp

    Or configure through the goose CLI using goose configure:

    ┌   goose-configure

    ◇ What would you like to configure?
    │ Configure Providers

    ◇ Which model provider should we use?
    │ Codex CLI

    ◇ Model fetch complete

    ◇ Enter a model from that provider:
    │ gpt-5.2-codex

Usage Examples

Basic Usage

goose session

Using with Extensions

Extensions configured via --with-extension or --with-streamable-http-extension are passed through to the ACP agent:

GOOSE_PROVIDER=claude-acp goose run \
--with-extension 'npx -y @modelcontextprotocol/server-everything' \
-t 'Use the echo tool to say hello'
GOOSE_PROVIDER=codex-acp goose run \
--with-streamable-http-extension 'https://mcp.kiwi.com' \
-t 'Search for flights from BKI to SYD tomorrow'

Configuration Options

Claude ACP Configuration

Environment VariableDescriptionDefault
GOOSE_PROVIDERSet to claude-acpNone
GOOSE_MODELModel to usedefault

Known Models:

  • default (opus)
  • sonnet
  • haiku

Permission Modes (GOOSE_MODE):

ModeSession ModeBehavior
autobypassPermissionsSkips all permission checks
smart-approveacceptEditsAuto-accepts file edits, prompts for risky operations
approvedefaultPrompts for all permission-required operations
chatplanPlanning only, no tool execution

See claude-agent-acp for session mode details.

Codex ACP Configuration

Environment VariableDescriptionDefault
GOOSE_PROVIDERSet to codex-acpNone
GOOSE_MODELModel to usegpt-5.2-codex

Known Models:

  • gpt-5.2-codex
  • gpt-5.2
  • gpt-5.1-codex-max
  • gpt-5.1-codex-mini

Permission Modes (GOOSE_MODE):

ModeApproval / SandboxBehavior
autoNo approvals, full accessBypasses all approvals and sandbox restrictions
smart-approveOn-request, workspace-writeWorkspace write access, prompts for operations outside sandbox
approveOn-request, read-onlyRead-only sandbox, prompts for all write operations
chatNo approvals, read-onlyRead-only sandbox, no tool execution

See codex-acp for approval policy and sandbox details.

Error Handling

ACP providers depend on external npm packages, so ensure:

  • The ACP adapter binary is installed and in your PATH (claude-agent-acp or codex-acp)
  • The underlying CLI tool is authenticated and working
  • Subscription limits are not exceeded
  • Node.js and npm are installed

If goose can't find the binary, session startup will fail with an error. Run which claude-agent-acp or which codex-acp to verify installation.