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.

:::tip Use Your Existing Subscriptions ACP providers let you use goose with your existing Claude Code or ChatGPT Plus/Pro subscriptions — no per-token API costs. They are the recommended replacement for the deprecated CLI providers. :::

:::warning 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

Amp ACP

Wraps amp-acp, an ACP adapter for Amp. Uses your existing Amp subscription.

Requirements:

Node.js and npm
Amp CLI installed (curl -fsSL https://ampcode.com/install.sh | bash)
ACP adapter installed (npm install -g amp-acp)
Authenticated with your Amp account (amp CLI working)

Claude ACP

Wraps claude-agent-acp, an ACP adapter for Anthropic's Claude Code. Uses the same Claude subscription as the deprecated 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 deprecated 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)

Pi ACP

Wraps pi-acp, an ACP adapter for Pi. Uses your existing Pi installation.

Requirements:

Pi CLI installed
ACP adapter installed (pi-acp binary available)
Authenticated with your Pi account (pi CLI working)

Setup Instructions

Amp ACP

Install the Amp CLI

bash

curl -fsSL https://ampcode.com/install.sh | bash

Install the ACP adapter
bash
```
npm install -g amp-acp
```
Authenticate with Amp

Run amp and follow the authentication prompts.
Configure goose

Set the provider environment variable:
bash
```
export GOOSE_PROVIDER=amp-acp
```
Or configure through the goose CLI using goose configure.

Claude ACP

Install the ACP adapter

bash

npm install -g @agentclientprotocol/claude-agent-acp

Authenticate with Claude

Ensure your Claude CLI is authenticated and working

Configure goose

Set the provider environment variable:

bash

export GOOSE_PROVIDER=claude-acp

Or configure through the goose CLI using goose configure:

bash

┌   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

Install the ACP adapter

bash

npm install -g @zed-industries/codex-acp

Authenticate with OpenAI

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

Configure goose

Set the provider environment variable:

bash

export GOOSE_PROVIDER=codex-acp

Or configure through the goose CLI using goose configure:

bash

┌   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

Pi ACP

Install the Pi CLI and ACP adapter

Install the pi CLI and the pi-acp ACP adapter following the project's installation instructions.
Authenticate with Pi

Run pi and follow the authentication prompts.
Configure goose

Set the provider environment variable:
bash
```
export GOOSE_PROVIDER=pi-acp
```
Or configure through the goose CLI using goose configure.

Usage Examples

Basic Usage

bash

goose session

Using with Extensions

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

bash

GOOSE_PROVIDER=claude-acp goose run \
  --with-extension 'npx -y @modelcontextprotocol/server-everything' \
  -t 'Use the echo tool to say hello'

bash

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

Amp ACP Configuration

Environment Variable	Description	Default
`GOOSE_PROVIDER`	Set to `amp-acp`	None
`GOOSE_MODEL`	Model to use	`current`
`GOOSE_MODE`	Permission mode	`auto`

Claude ACP Configuration

Environment Variable	Description	Default
`GOOSE_PROVIDER`	Set to `claude-acp`	None
`GOOSE_MODEL`	Model to use	`default`
`GOOSE_MODE`	Permission mode	`auto`

Known Models:

default (opus)
sonnet
haiku

Permission Modes (GOOSE_MODE):

Mode	Session Mode	Behavior
`auto`	`bypassPermissions`	Skips all permission checks
`smart-approve`	`acceptEdits`	Auto-accepts file edits, prompts for risky operations
`approve`	`default`	Prompts for all permission-required operations
`chat`	`plan`	Planning only, no tool execution

See claude-agent-acp for session mode details.

Codex ACP Configuration

Environment Variable	Description	Default
`GOOSE_PROVIDER`	Set to `codex-acp`	None
`GOOSE_MODEL`	Model to use	`gpt-5.2-codex`
`GOOSE_MODE`	Permission mode	`auto`

Known Models:

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

Permission Modes (GOOSE_MODE):

Mode	Approval / Sandbox	Behavior
`auto`	No approvals, full access	Bypasses all approvals and sandbox restrictions
`smart-approve`	On-request, workspace-write	Workspace write access, prompts for operations outside sandbox
`approve`	On-request, read-only	Read-only sandbox, prompts for all write operations
`chat`	No approvals, read-only	Read-only sandbox, no tool execution

See codex-acp for approval policy and sandbox details.

Pi ACP Configuration

Environment Variable	Description	Default
`GOOSE_PROVIDER`	Set to `pi-acp`	None
`GOOSE_MODEL`	Model to use	`current`
`GOOSE_MODE`	Permission mode	`auto`

Error Handling

ACP providers depend on external binaries, so ensure:

The ACP agent binary is installed and in your PATH (amp-acp, claude-agent-acp, codex-acp, pi-acp, or copilot)
The underlying CLI tool is authenticated and working
Subscription limits are not exceeded
Node.js and npm are installed (for npm-distributed adapters)

If goose can't find the binary, session startup will fail with an error. Run which <binary> to verify installation.