Paperclip can turn Claude quota waits into 110 permanent blocked tickets a day

paperclipai/paperclip issue #10344 is the inspected primary source: “Recovery misclassifies Claude session/weekly-limit failures as stuck work, minting permanent `blocked` issues instead of using the existing provider-quota wait.” Issue #10344 reproduces against server release 2026.722.0 and canary 2026.728.0-canary.1. Claude limit failures arrive as acpx_turn_failed, but the recovery classifier only examines provider-quota text after accepting adapter_failed. Even if that code gate were widened, the patterns recognize usage, rate and quota limits but not Claude’s actual “session limit” or “weekly limit” wording. The two gaps therefore fail independently. Misclassified work enters blocked without a dependency edge or monitor and can be reassigned to a recovery owner who cannot clear the provider condition. The reporter counted roughly 110 artifacts per day and found they represented 66% of the blocked backlog. Paperclip already has an ensureProviderQuotaWaitRecoveryMonitor path that schedules a retry and avoids minting a notice; this input never reaches it. Closed docs PR #10094 now says blocked work requires a routable waiting path and bounded watchdog restoration. Closed UI PR #10225 exposes an activity gate so scheduled routines can skip quiet ticks and explain the reason.

The facts

- paperclipai/paperclip issue #10344 was created 2026-07-28T00:36:20Z and updated 2026-07-28T00:36:20Z; state is open. - paperclipai/paperclip returned 74911 GitHub stars, 4937 open issues, default branch master, and last push 2026-07-28T00:58:13Z. - Latest tagged-release baseline checked: v2026.722.0 published 2026-07-22T23:05:41Z. - Issue #10344 reproduces against server release 2026.722.0 and canary 2026.728.0-canary.1. - Claude limit failures arrive as acpx_turn_failed, but the recovery classifier only examines provider-quota text after accepting adapter_failed. - Even if that code gate were widened, the patterns recognize usage, rate and quota limits but not Claude’s actual “session limit” or “weekly limit” wording. - The two gaps therefore fail independently. - Misclassified work enters blocked without a dependency edge or monitor and can be reassigned to a recovery owner who cannot clear the provider condition.

What changed

Issue #10344 reproduces against server release 2026.722.0 and canary 2026.728.0-canary.1. Claude limit failures arrive as acpx_turn_failed, but the recovery classifier only examines provider-quota text after accepting adapter_failed. Even if that code gate were widened, the patterns recognize usage, rate and quota limits but not Claude’s actual “session limit” or “weekly limit” wording. The two gaps therefore fail independently. Misclassified work enters blocked without a dependency edge or monitor and can be reassigned to a recovery owner who cannot clear the provider condition. The reporter counted roughly 110 artifacts per day and found they represented 66% of the blocked backlog. Paperclip already has an ensureProviderQuotaWaitRecoveryMonitor path that schedules a retry and avoids minting a notice; this input never reaches it. Closed docs PR #10094 now says blocked work requires a routable waiting path and bounded watchdog restoration. Closed UI PR #10225 exposes an activity gate so scheduled routines can skip quiet ticks and explain the reason. The primary record was inspected with its timestamps, state, body and adjacent project records. ClawCharts supplied the assignment list; it does not establish the claim.

Why it matters

A control plane becomes unusable when transient capacity errors are converted into permanent workflow state. The cost is not only queue noise: reassignment hides work from the seat that owns the provider session, distorts backlog metrics and trains operators to ignore blocked status. This is classification debt turning into organizational debt. The useful boundary is where persisted state, visible control and runtime behavior are expected to agree.

Current

The issue was open when inspected. The reporter explicitly checked both current latest and current canary packages. The supporting documentation and activity-gate records were closed, but neither is evidence that quota classification changed. The latest stable GitHub release baseline was v2026.722.0. Repository metadata, current issues and pull requests, release baseline, Hacker News discovery and the rendered ranking row were checked. Weak search residue and historically used source spines were not promoted.

Evidence

The primary URL is https://github.com/paperclipai/paperclip/issues/10344. Supporting links are inspected current project records that establish implementation, adjacent direction or boundary conditions. Dates, reproductions, test totals and deployment observations remain attributed to their authors unless this brief explicitly says they were independently rerun.

Source boundary

Open work is described as open, closed work as closed, and operator reports as reports. Closure can reflect a documentation decision or triage outcome; it is not silently translated into a shipped code fix. Ranking explains why the project was scanned; it does not prove correctness, adoption or package behavior.

Operator take

Model provider exhaustion as a timed wait with an owner, retry deadline and evidence of the reset condition. Preserve the original assignee unless a real human decision changes ownership. Audit blocked rows for missing dependency edges, missing monitors and provider-limit vocabulary before trusting backlog counts. Preserve a before-state receipt and verify the narrowest invariant where state changes. Do not broaden permissions or delete state merely because the visible symptom is inconvenient.

Caveat

Public project records are mutable. Source state was captured at publication time, and later revisions may change status, scope or evidence. No source here authorizes automatic mutation of a reader’s deployment.

Source inspected; source state, environment and release boundary remain explicit.