feat: add gemini-acp provider, update docs on subscription models + improvements to codex (#8000)

Signed-off-by: Michael Neale <michael.neale@gmail.com>
2026-03-19 13:20:45 +11:00
parent 4e7a572497
commit 5be96c1ab2
12 changed files with 269 additions and 18 deletions
@@ -0,0 +1,74 @@
+---
+title: "Use Goose with Your AI Subscription"
+description: "A quick update on using subscriptions for claude, gemini and codex"
+authors: 
+    - mic
+---
+
+You can use your subscriptions for codex, claude and gemini now with goose, thanks to ACP! (Agent Client Protocol).
+Codex is also special in that you can login directly to chatgpt - nothing else needs to be installed. 
+
+Gemini natively supports ACP, so it now works with a gemini acp provider in goose. At the time of writing, claude requires just one utility installed just once.
+
+<!--truncate-->
+
+## Why subscriptions?
+
+Well you can use what you already pay for. Obviously! and sessions and so on are still in goose. 
+ACP gives a deeper connection to these agents than using the CLI as providers. In this world - you can think of this as a stack of agents: 
+goose plugs into gemini via ACP (and other things, clients could plug in to goose!) but gemini (and also claude code) also act as an agent loop somewhat. 
+With ACP you are using the tools that are (mostly) in the underlying agent. Codex, however, is a full power LLM api, so you can use extensions natively in goose for that one.
+
+## Claude Code — via ACP
+
+If you have a Claude Code subscription, you can use it through goose via the [Agent Client Protocol (ACP)](https://agentclientprotocol.com/). This requires installing a small adapter package:
+
+```bash
+npm install -g @zed-industries/claude-agent-acp
+```
+
+Then configure goose to use it via the claude acp extension (CLI or GUI)
+
+
+Or set it via environment variables:
+
+```bash
+export GOOSE_PROVIDER=claude-acp
+goose
+```
+
+goose passes your MCP extensions through to Claude via ACP, so any custom MCP servers you've configured in goose are available to the agent.
+
+## ChatGPT — sign in with your account
+
+If you have ChatGPT Plus or Pro, the `chatgpt_codex` provider lets you use goose with your existing account. Just pick ChatGPT when you are setting up the goose app for the first time (or changing to that provider)
+
+The first time you run it, goose will open a browser window for you to sign in with your ChatGPT account. After that, your session is cached locally.
+
+The recommended model is `gpt-5.3-codex`, which is the default. You can also select `gpt-5.4` (OpenAI's latest omni model) or `gpt-5.2-codex` from the model picker.
+
+## Gemini — via ACP (native)
+
+If you have a Google account with Gemini access, the Gemini CLI speaks ACP natively — no separate adapter needed. Just install the Gemini CLI itself:
+
+```bash
+npm install -g @google/gemini-cli
+```
+
+... and run `gemini` at least once. 
+
+On first run, Gemini CLI will ask you to authenticate with your Google account. After that, goose passes your extensions directly through to Gemini via ACP. 
+
+## What about the old CLI providers?
+
+Goose previously supported `claude-code`, `codex`, and `gemini-cli` as "pass-through" CLI providers. These will be removed soon as ACP is the future! 
+
+## Quick reference
+
+| Subscription | Provider | Install | Extensions |
+|---|---|---|---|
+| Claude Code | `claude-acp` | `npm install -g @zed-industries/claude-agent-acp` | ✅ via MCP |
+| ChatGPT Plus/Pro | `chatgpt_codex` | Nothing — OAuth sign-in | ✅ via MCP |
+| Gemini | `gemini-acp` | `npm install -g @google/gemini-cli` | ✅ via MCP |
+
+Pick the one that matches what you're already paying for, and you're good to go.