Nous Research reportedly released an experimental Claude Subscription DirectSDK plugin for Hermes that preserves Hermes tools and memory while using Claude subscription access, potentially eliminating cross-harness conversation transfers.
state: corroboratedheat: highuncertainty: mediumknownscott: lowagent-harnesses model-routing agent-memoryNous ResearchAnthropic
Surfaced 2026-09-24T05:17:28Z — Claude Subscriptions Back In Hermes! — The case graduates from rumor to corroborated mechanism — Nous's official plugin is grounded and independently exercised at long context — but its meaning has shifted from capability to fragility: PrimeIntellect's first-party warning that subscription-auth requests identify as Claude Code and risk account bans turns 'authorization unclear' into a named enforcement risk, with the ~29× cache-write defect as the standing economic caveat.
What is this?
Nous Research has published an official, experimental Hermes Agent plugin, 'claude-subscription-directsdk' (added ~Sep 20, 2026), that lets Hermes Agent runs use Claude Pro/Max subscription billing instead of an API key. It works by driving the unmodified official Claude Code CLI as a request-scoped model client — spawning a fresh claude process per request and speaking native stream-json — while Hermes keeps its own agent loop, tools, approvals, and compaction. This restores Claude access that had previously been shut off, leaving API-key billing as the only path. Notable caveat: an open GitHub issue reports the provider freezes the prompt-cache prefix and re-writes the transcript every tool round (~29× more cache writes than native Claude Code), a real cost/efficiency defect for a subscription-billed path.
Why it matters to Scott
The radar already tracks Hermes Agent as an open case (radar:hermes-agent-open-harness), and the underlying move — pooling Claude/subscription access behind a harness-compatible endpoint to dodge API metering — is already covered by the Underclass proxy, CodePress subscription-workflow, and Claude Code usage-limit-cut episodes; ToS/exposure risk for CLI-as-provider plumbing is likewise on file (Moonshot allegation, malicious-router episodes). Scott already operates this exact pattern himself ('ask' shells out to codex CLI as its default model client behind LiteLLM routing), so the pattern is confirmation, not news. The one genuinely new datapoint is the reported prompt-cache defect (~29× cache writes from transcript rewriting per tool round), which is relevant to his prompt-caching and token-economics tracking and his subscription-vs-API pricing arguments — but it's a defect report on a story the radar already holds, not a new position or a consequential party arriving anywhere Scott hasn't already been.
dev:project.askdev:technology.claude-codedev:concept.task-aware-model-routingdev:project.llmreportradar:hermes-agent-open-harnessradar:underclass-sticky-subscription-poolradar:codepress-subscription-cloud-agentsradar:claude-code-usage-limit-cutradar:concept.prompt-caching
queries asked of Scott's wikis
- harness model-routing: swapping frontier models behind one agent loop without losing tools/memory
- subscription-vs-API economics for agent workloads (Claude Pro/Max Agent SDK allowance, prompt-cache costs)
- shelling out to a vendor CLI as a model provider — portability and ToS risk patterns
- agent memory continuity across model swaps: does provider choice break persistent memory/compaction?
- prior positions on harness-agnostic agent architecture / 'the harness is the product' claims
- hermes/hume dev projects: model-provider plugin architecture, profile system, provider abstraction
Measured heat
now 0 pts/hpeak 0 pts/hcomments 0/hpeers p0momentum: steady2 platformsage 453h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
| 09-22 18:47 | ⭐ origin directly observed | Claude Subscriptions Back In Hermes! myLifeintheStack on r/ClaudeAI | — |
| 09-24 01:01 | first on github · published · +30.2h | v0.9.6 github-actions[bot] | — |
| 09-22 18:47 | amplified on r/ClaudeAI | reddit.post.1wni5yd myLifeintheStack | peak 10 · 11 comments · 7% of case engagement |
| 09-24 01:01 | amplified on github 👑 | github.release.PrimeIntellect-ai.prime-agent.v0.9.6 github-actions[bot] | peak 21247 · 0 comments · 93% of case engagement |
| 09-22 19:20 | our radar first saw it · +0.6h | discovery anchor: reddit.post.1wni5yd | — |
| 09-24 05:12 | reached heat=high · +34.4h · via queue+ledger | — | — |
pace: p100 vs 1032 stories at the 336h mark (now 453h old) — ahead of prime-agent-090-atomic-repl-state (1.1x), behind anthropic-opus-55-website-signal (1.0x)
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-09-24T05:12:20Z
magnitude valve eligible (multi-platform, top-decile engagement) and never alerted; deterministic escalation to deliver
2026-09-24T04:28:12Z
evidence attached: github.release.PrimeIntellect-ai.prime-agent.v0.9.6 — PrimeIntellect's first-party warning that third-party harnesses using Claude subscription access identify as Claude Code and risk account bans is material risk context for the subscription-backed cross-harness approach.
2026-09-23T19:41:38Z
grounded: known/low — The radar already tracks Hermes Agent as an open case (radar:hermes-agent-open-harness), and the underlying move — pooling Claude/subscription access behind a h
2026-09-23T10:24:01Z
case created — A named experimental integration and reported long-context use establish a bounded interoperability episode, although authorization and durability remain unclear.
Decision trace
- 09-28 22:30review_screenjev screen: no material development (noul=0.05)
- 09-24 15:17pushClaude Subscriptions Back In Hermes! — The case graduates from rumor to corroborated mechanism — Nous's official plugin is grounded and independently exercised at long context — but its meaning h
- 09-24 15:12repriceThe case graduates from rumor to corroborated mechanism — Nous's official plugin is grounded and independently exercised at long context — but its meaning has shifted from capability to fragility
- 09-24 15:12alert_heldClaude Subscriptions Back In Hermes! — The case graduates from rumor to corroborated mechanism — Nous's official plugin is grounded and independently exercised at long context — but its meaning h
- 09-24 15:12alert_routeClaude Subscriptions Back In Hermes! — The case graduates from rumor to corroborated mechanism — Nous's official plugin is grounded and independently exercised at long context — but its meaning h
- 09-24 14:28attachPrimeIntellect's first-party warning that third-party harnesses using Claude subscription access identify as Claude Code and risk account bans is material risk context for the subscription-backed
- 09-24 14:25propose_attachPrimeIntellect's first-party warning that third-party harnesses using Claude subscription access identify as Claude Code and risk account bans is material risk context for the subscription-backed
- 09-24 05:41groundThe radar already tracks Hermes Agent as an open case (radar:hermes-agent-open-harness), and the underlying move — pooling Claude/subscription access behind a harness-compatible endpoint to dodge API
- 09-24 04:15createA named experimental integration and reported long-context use establish a bounded interoperability episode, although authorization and durability remain unclear.