Correct stale Claude Max ToS note in docs/substrate.md #16

Open
opened 2026-05-23 21:11:18 +00:00 by coilysiren · 0 comments
Owner

Target - docs/substrate.md, the "ToS context" section
Type - doc correction, factual accuracy only, blocks no work

Problem

The note says out-of-band orchestration using Claude Max OAuth was banned April 2026, with the plugin path framed as the only Max-touching path. That is stale. Anthropic reversed the hard prohibition on May 13 2026 and replaced it with a metered-credit model, effective June 15 2026.

Accurate state as of late May 2026

  • Jan 2026 - enforcement start - subscription OAuth tokens blocked from third-party harnesses and the Agent SDK. Token extraction or harness spoofing triggered bans.
  • April 4 2026 - hard ban - subscriptions prohibited from powering third-party agents, citing compute strain. Still allowed via pay-as-you-go extra usage or the API.
  • May 13 2026 - reversal - programmatic usage moves to a separate non-rollover monthly Agent SDK credit, effective June 15 2026, metered at API list rates.
  • Credit tiers - Pro $20, Max 5x $100, Max 20x $200, Team $100 per seat, Enterprise $200 per seat. Unused credit expires at month end.
  • Scope of the credit pool - the claude -p non-interactive command, Claude Code GitHub Actions, and third-party apps that auth through the Agent SDK.
  • Stays on interactive subscription limits - interactive Claude Code, Cowork, and chat. The plugin path for luca is unaffected.

Implication for the substrate

The plugin path is still the right call for luca, but the reason changes. It is no longer the only legal way to touch Max. It is the way that stays on interactive subscription economics instead of draining a metered API-rate credit. An always-on programmatic fleet on claude -p would burn the credit fast at API rates, so API keys or local vLLM remain the backend for 24/7 work.

Action

Replace the "banned April 2026" line with the metered-credit summary above. The historical ban timeline goes in git history, not the doc body.

Target - docs/substrate.md, the "ToS context" section Type - doc correction, factual accuracy only, blocks no work Problem The note says out-of-band orchestration using Claude Max OAuth was banned April 2026, with the plugin path framed as the only Max-touching path. That is stale. Anthropic reversed the hard prohibition on May 13 2026 and replaced it with a metered-credit model, effective June 15 2026. Accurate state as of late May 2026 * Jan 2026 - enforcement start - subscription OAuth tokens blocked from third-party harnesses and the Agent SDK. Token extraction or harness spoofing triggered bans. * April 4 2026 - hard ban - subscriptions prohibited from powering third-party agents, citing compute strain. Still allowed via pay-as-you-go extra usage or the API. * May 13 2026 - reversal - programmatic usage moves to a separate non-rollover monthly Agent SDK credit, effective June 15 2026, metered at API list rates. * Credit tiers - Pro $20, Max 5x $100, Max 20x $200, Team $100 per seat, Enterprise $200 per seat. Unused credit expires at month end. * Scope of the credit pool - the claude -p non-interactive command, Claude Code GitHub Actions, and third-party apps that auth through the Agent SDK. * Stays on interactive subscription limits - interactive Claude Code, Cowork, and chat. The plugin path for luca is unaffected. Implication for the substrate The plugin path is still the right call for luca, but the reason changes. It is no longer the only legal way to touch Max. It is the way that stays on interactive subscription economics instead of draining a metered API-rate credit. An always-on programmatic fleet on claude -p would burn the credit fast at API rates, so API keys or local vLLM remain the backend for 24/7 work. Action Replace the "banned April 2026" line with the metered-credit summary above. The historical ban timeline goes in git history, not the doc body.
coilysiren added
P4
and removed
P3
labels 2026-05-31 07:00:07 +00:00
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/agentic-os#16
No description provided.