Cairn

Claude Code CLI/SDK as native subscription provider

NousResearch/hermes-agent · cluster 12122 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

2open issues
2open PRs
12items grouped
Known?
Yes. 12 related items grouped here, 7 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 2 PRs.

Multiple requests and proposals to integrate Claude Code CLI and/or the Anthropic Agent SDK as a first-class provider, enabling routing through local subprocess execution using Max/Pro subscription OAuth credentials rather than API keys.

Open issues2

  • Issue#25267[Feature]: Claude Agent SDK model provider with subscription OAuth (Codex-style)
  • Issue#52362[Feature]: Claude SDK as Backend

Open PRs2

  • PR#65982feat(providers): claude-agent-sdk provider — the official Agent SDK as a first-class runtime under subscription OAuth (fail-closed)
  • PR#98533feat: claude-code-cli provider — Claude subscription via the Claude Code CLI with real tool calls

1 PR closed without merging

From the close comments: other 1

  • #12124 feat(gateway): add `/cc` command to route messages to Claude Code CLI · other → eb9db0c
Closed issues · 7
  • Closed#12122feat(gateway): `/cc` command — route messages to Claude Code CLI without going through Hermes
  • Closed#16923[Feature]: claude-cli backend provider just like openclaw
  • Closed#31385Proposal: Subprocess executor bridge for delegating gateway turns to Claude Code CLI
  • Closed#32392[Feature]: Feature Request: Support Claude Code / Claude Team Authentication as Hermes Provider
  • Closed#33462feat(provider): register `claude-code` as first-class subprocess provider (Claude Max OAuth via local CLI)
  • Closed#33537Register `claude-code` as first-class provider for native streaming + tool_use (currently alias-only)
  • Closed#48320Feature Request: claude-code provider that shells out to claude -p for Max/Pro subscription quota
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.14: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
7
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/12122.json
cluster/12122.md