"The operation couldn’t be completed. (Swift.CancellationError error 1.)" for Claude Edu subscribers

[singularitti]

I'm using a Claude Edu subscription and logged in through web UI in both the Claude desktop app and claude-code CLI. I can use them normally. However, none of them were detected correctly in the menubar stats or macOS desktop widgets. I saw multiple errors, one of which is "Could not parse Claude usage: Claude CLI /usage returned a subscription notice without session quota data." But I can see the chart or the cost. Is this a bug?

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed July 1, 2026, 4:18 AM ET / 08:18 UTC.

Summary
Keep open: current main still intentionally surfaces the reported Claude CLI subscription-notice path as a no-quota parse failure, and the screenshots show a plausible configuration/setup gap rather than an already-fixed behavior.

Reproducibility: Partly yes: current source and tests reproduce the exact CLI subscription-notice parse failure. No high-confidence live current-main reproduction shows a fully configured Claude Edu Web/OAuth source failing with unsupported payload data.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Next step
This should not be queued automatically until a maintainer confirms whether the reporter has Web/OAuth configured and captures a redacted Edu diagnostic payload.

Review details

Best possible solution:

Have a maintainer request redacted Claude diagnostics and verify a configured Claude Edu Web/OAuth source; then either add focused parser support for the observed payload or improve the recovery copy for keychain-disabled/manual-cookie setups.

Do we have a high-confidence way to reproduce the issue?

Partly yes: current source and tests reproduce the exact CLI subscription-notice parse failure. No high-confidence live current-main reproduction shows a fully configured Claude Edu Web/OAuth source failing with unsupported payload data.

Is this the best way to solve the issue?

Unclear: the current CLI classification is intentional because the CLI notice contains no session quota data. The maintainable path is to diagnose whether Web/OAuth is unconfigured, unavailable because Keychain access is disabled, or returning a new Edu payload shape before changing provider behavior.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The screenshots show Keychain access disabled, Claude cookies set to Manual, and no token accounts yet, so this may be a setup/recovery-guidance issue rather than a parser bug in a fully configured Edu account.
• A real Claude Edu account and redacted diagnostics are still needed to know whether OAuth/Web returns a usable quota payload with unsupported fields or whether the app is behaving as configured.

Codex review notes: model internal, reasoning high; reviewed against d3f2d6433026.

Label changes

Label changes:

• add P2: Claude Edu usage detection appears blocked for one provider/account shape, but local cost data still renders and there is no evidence of app-wide outage.
• add impact:auth-provider: The issue centers on Claude authentication/source routing and whether OAuth, CLI, or Web credentials can provide subscription utilization.
• add issue-rating: 🐚 platinum hermit: Current issue advisory state selects this label.
• add clawsweeper:needs-live-repro: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

Label justifications:

• P2: Claude Edu usage detection appears blocked for one provider/account shape, but local cost data still renders and there is no evidence of app-wide outage.
• impact:auth-provider: The issue centers on Claude authentication/source routing and whether OAuth, CLI, or Web credentials can provide subscription utilization.

Evidence reviewed

Acceptance criteria:

• CodexBarCLI diagnose --provider claude --format json --pretty with secrets redacted
• swift test --filter TTYIntegrationTests
• swift test --filter ClaudeDirectUsageFallbackTests
• swift test --filter ClaudeWebEnterpriseUsageTests
• swift test --filter ClaudeOAuthTests

What I checked:

• Repository policy read: AGENTS.md was read fully; its guidance is relevant because this is Claude provider/parser behavior and live account, Keychain, and provider probes should not be run without explicit request. (AGENTS.md:1, d3f2d6433026)
• Current source surfaces the exact CLI error: ClaudeStatusProbe maps subscription-only Claude CLI /usage output to “Claude CLI /usage returned a subscription notice without session quota data.”. (Sources/CodexBarCore/Providers/Claude/ClaudeStatusProbe.swift:464, d3f2d6433026)
• Current tests expect subscription-only CLI output to fail parsing: The TTY integration test builds a fake Claude CLI that prints the same subscription notice and asserts the probe fails with a subscription-related parse error. (Tests/CodexBarTests/TTYIntegrationTests.swift:75, d3f2d6433026)
• Current fallback source order and web setup are documented: docs/claude.md documents app auto as OAuth API → CLI PTY → Web API, and documents that manual web mode requires a claude.ai Cookie header/sessionKey. (docs/claude.md:20, d3f2d6433026)
• Reporter screenshots show a narrower setup/state issue: The screenshots show source Auto, the subscription-notice error, cost/log-derived charts, Claude cookies set to Manual, Keychain access disabled, and no token accounts yet, so web/OAuth may not be configured even though local cost data renders.
• History provenance for subscription-notice handling: git log -S shows commit 126dc92 introduced the current explicit subscription-only handling as a prior fix, so the present issue is about the remaining Edu/provider setup gap rather than missing that classification. (Sources/CodexBarCore/Providers/Claude/ClaudeStatusProbe.swift:464, 126dc9238715)

Likely related people:

• Yuxin-Qiao: Commit 126dc92 added the explicit Claude CLI subscription-only parse classification and related tests. (role: introduced subscription-notice handling; confidence: high; commits: 126dc9238715; files: Sources/CodexBarCore/Providers/Claude/ClaudeStatusProbe.swift, Sources/CodexBarCore/Providers/Claude/ClaudeUsageFetcher.swift, Tests/CodexBarTests/TTYIntegrationTests.swift)
• steipete: Recent current-main Claude OAuth/source isolation commits and related issue comments route this area through steipete, including c57de22 and the maintainer retest on the related no-strategy report. (role: recent area contributor and repository owner; confidence: high; commits: c57de22c9ffe, 92bbb7a67073, f380287041b8; files: Sources/CodexBarCore/Providers/Claude/ClaudeUsageFetcher.swift, Sources/CodexBarCore/Providers/Claude/ClaudeWeb/ClaudeWebAPIFetcher.swift, docs/claude.md)
• Derek Zeng: Commit 3bc9781 recently changed Claude OAuth usage isolation and delegated refresh behavior near the source-selection/auth path. (role: recent adjacent OAuth contributor; confidence: medium; commits: 3bc978114747; files: Sources/CodexBarCore/Providers/Claude/ClaudeUsageFetcher.swift, Tests/CodexBarTests/ClaudeOAuthDelegatedRefreshRecoveryTests.swift)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[steipete]

Fixed on main by #1813 (c3d33308ac0624424bd8c089d9eff59f3701aefa).

Claude Education and organization-managed subscription notices without numeric quotas are now treated as an informational “Limits not available” state instead of a provider failure. Expected cancellation stays silent, CLI-confirmed unavailability no longer falls through to web, local Claude cost/token history remains available to menus and widgets, and the status icon stops animating once that state is known.

Proof: 53 focused tests, all 44 local shards, make check, exact package/signature/launch and in-bounds Peekaboo menu validation, two clean final autoreviews, and exact-head CI run 28539755548 with all 10 status contexts green.