Files

Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)

Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.

2026-10-06 01:47:40 +02:00

6.7 KiB

Raw Permalink Blame History

Provider rate-limit signals across executor runtimes

Status: research note — informs #3095 reactive classification and points at the proactive path forward.

MSD dispatches executor subagents into one of four host runtimes today: Claude Code, GitHub Copilot CLI, OpenAI Codex CLI, and Antigravity CLI (Google Gemini backend). Each provider exposes rate-limit information at three different layers — pre-warning, post-mortem error body, and underlying HTTP transport — but the host runtime (the CLI that wraps the provider for us) gates how much of that surfaces to MSD's orchestrator.

The reactive classifier shipped with #3095 (agent.classify-failure) parses post-mortem error bodies. This note records the proactive signals that exist at the provider layer but are not yet surfaced to orchestrators by the host runtimes — i.e. the forward path once host runtimes expose them to hooks.

Anthropic / Claude Code

Layer	Signal	Available to MSD today?
HTTP headers	`anthropic-ratelimit-requests-remaining`, `anthropic-ratelimit-tokens-remaining`, `retry-after` on 429	No — Claude Code does not forward these to hooks (#33820, #22407)
Agent SDK	`RateLimitEvent` with `status` transitions: `allowed` → `allowed_warning` → `rejected`	Only when callers use the Agent SDK directly
Plan usage	Max plan session / weekly usage	No — Claude Code SDK does not expose Max-plan limits (#32796)
Error body	`"You've hit your org's monthly usage limit"`, `429`, `rate_limit_error`	Yes — parsed by `agent.classify-failure`

GitHub Copilot CLI

Layer	Signal	Available to MSD today?
Pre-warning	CLI displays a warning when approaching a limit (per GitHub Copilot usage-limits docs)	Visible in subprocess stdout, not as a structured signal
Error body	`"hit a rate limit"`, `"exceeded your Copilot token usage"`, `rate_limited`, `user_weekly_rate_limited`	Yes — parsed by `agent.classify-failure`

OpenAI Codex CLI

Layer	Signal	Available to MSD today?
HTTP headers	`x-ratelimit-remaining-requests`, `x-ratelimit-remaining-tokens`	No — Codex CLI does not forward these to hooks
Error body	`429`, `usage_limit_reached`, `"exceeded your current quota"`, `Too Many Requests` (openai/codex#9135)	Yes — parsed by `agent.classify-failure`

Google Gemini (via Antigravity CLI)

Host runtime: Antigravity CLI. MSD's Gemini CLI runtime was removed in #1928 after Google sunset it on 2026-06-18; Antigravity is the documented successor and runs on the same Gemini backend, so the provider-layer signals below are unchanged.

Layer	Signal	Available to MSD today?
Error body	`RESOURCE_EXHAUSTED`, `"exceeded your current quota"`, `429`	Yes — parsed by `agent.classify-failure`
Pre-warning	None documented at the CLI layer	n/a

Forward path

When the host runtimes (Claude Code, Copilot CLI, Codex CLI) start exposing rate-limit headers and SDK events to hooks — which is the active ask in anthropics/claude-code#33820, #22407, and #32796 — MSD should:

Read requests-remaining / tokens-remaining in a PreToolUse / SessionStart hook and surface a soft warning to the user before dispatching a new wave when the values fall below a configurable threshold.
Treat RateLimitEvent.status == "allowed_warning" (Anthropic Agent SDK) as a checkpoint signal in long-running executors — emit a partial SUMMARY and let the orchestrator pick up after reset.
Combine the proactive headers with executor.stall_threshold_minutes (#3329) so the orchestrator does not wait the full stall interval when the runtime has already signalled rejected.

Until then, agent.classify-failure is the actionable boundary: post-mortem error-body sentinels, with a quota-distinct recovery prompt in execute-phase step 7.

6.7 KiB Raw Permalink Blame History