Using a Claude subscription

If you pay for Claude Pro or Max and have the claude CLI installed, OpenCues can route its prose-heavy surfaces through your subscription instead of a separate ANTHROPIC_API_KEY. Per-feature opt-in: fast surfaces stay on your fast provider.

Setup

Confirm the CLI works, then name it as a provider.

claude auth status > Logged in as you@example.com

Then in ~/.cues/OPENCUES.md:

agent-provider: claude-code-cli agent-model: haiku

No further setup: the next agent rewrite spawns a background claude process and routes the call through it; later calls reuse the same process, so the prompt cache stays warm. opencues doctor checks the binary is on your PATH.

Model names

Aliases track the latest release; full names pin one version.

ValueMeaning
haiku / sonnet / opus / fablethe latest release of that family, automatically
claude-haiku-4-5-20251001pinned to one version: your config keeps the same model when a new generation ships

Which model for which surface

Measured wall-clock through the CLI.

modeltypicalfits
haiku~840mstransforms, _ fills, agent rewrites
sonnet~1.3sagent rewrites
opus~2sagent rewrites when quality matters most

Word alternatives are not supported through the subscription route: they need an answer in under half a second, and even Haiku through the CLI is over that budget. Leave them on a fast provider, and mix freely:

llm-provider: cerebras llm-model: gpt-oss-120b agent-provider: claude-code-cli agent-model: sonnet

What to know

QuestionAnswer
does it use my quota?yes, calls count against your Pro or Max limits like any other CLI use
does OpenCues see my conversations?no; each call is independent, carrying only the text being rewritten
the browser extension?no; a browser cannot spawn the CLI, so chrome keeps using API providers
if my login expires?surfaces using it pause until you run claude auth again; the next call recovers on its own