OAuth tokens from ccr_inference (Cowork/CCD scheduled tasks) accumulate without cleanup
Status Closed — not planned
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 11 comments · opened Mar 24, 2026 · closed Apr 22, 2026
Description
OAuth tokens created by Claude Desktop's background Claude Code Runner sessions (ccr_inference) accumulate on the account without being revoked when the background session ends. Over normal usage, 30+ stale tokens pile up visible at https://claude.ai/settings/claude-code.
Steps to Reproduce
- Enable
coworkScheduledTasksEnabledandccdScheduledTasksEnabledin Claude Desktop config (both default totrue) - Use Claude Desktop normally for a few days
- Visit https://claude.ai/settings/claude-code
- Observe 30+
ccr_inferencesessions listed, most from completed/dead background runs
Expected Behavior
Background ccr_inference sessions should revoke their OAuth token when the session completes or is cleaned up. The settings page should show only active sessions.
Actual Behavior
Every background session creates a new OAuth token that persists indefinitely. No automatic cleanup occurs. There is also no "Revoke All" button to bulk-clear them.
Environment
- Claude Desktop v1.1.8359
- Claude Code v2.1.78
- macOS 15 (Darwin 25.3.0)
Additional Context
- No
revoke alloption exists on the settings page — users must click through each one individually - The accumulation is confusing and looks like session stealing to users who notice it
- Feature request: either auto-revoke on session end, or add a "Revoke All" bulk action
11 Comments
Screenshot Evidence
The settings page shows two distinct token types accumulating:
user:ccr_inference— minimal-scope tokens from Cowork/CCD background sessions (3 created within 1 minute of each other)user:file_upload,user:inference,user:mcp_servers,user:profile,user:sessions:claude_code) — from regular Claude Code CLI sessions, also accumulating without cleanupThe visible page shows ~10 tokens in just the last hour. Scrolling reveals many more going back days/weeks. No bulk revoke option exists — each must be deleted individually via the trash icon.
This confirms the tokens are never auto-revoked when sessions end, regardless of whether it's a background
ccr_inferencesession or a normal CLI session.Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Additional Finding: Token Revocation Cascade
Revoking stale
ccr_inferencetokens from the settings page also kills the active Claude Code CLI session, forcing a re-login. This suggests:ccr_inferencesessions and active CLI sessions may share a refresh token chainThis makes the token accumulation problem worse — not only do tokens pile up, but attempting to manually clean them up causes active session disruption.
Also observed: a Cloudflare MCP OAuth popup appeared unprompted with no Claude Code sessions actively running. The
cloudflare-bindingsandcloudflare-buildsMCP servers are bundled SDK servers with no user toggle to disable them. Backgroundccr_inferencesessions may be triggering MCP auth flows autonomously.Correction: Forced Re-login Without User Action
The active CLI session was forced to re-login without any manual token revocation. No tokens were revoked from the settings page. This means:
ccr_inferencesessions spawning may be rotating/invalidating the active session's OAuth tokenThis is the original reported symptom: recurring forced logouts every ~10 minutes with no user action. The token accumulation on the settings page is a symptom of the same root cause — background sessions are churning through OAuth tokens and destabilizing the active session.
Workaround (Destructive)
The only current workaround is to disable both Cowork features in
claude_desktop_config.json:This stops the forced logouts but completely disables the Cowork/CCD scheduled tasks feature. Users shouldn't have to choose between background tasks and a stable active session.
Onset: Started After Latest Claude Desktop Update
This issue began after updating to Claude Desktop v1.1.8359. The user had been running for months without forced logouts prior to this update. The Cowork/CCD scheduled tasks feature likely changed its OAuth token handling in this release.
Full Version Info
Not a Duplicate — Different Severity
This issue is related to but distinct from #28214 and #34198:
Additional findings unique to this issue:
ccr_inferencesessions rotate tokensworkaround in #4 does not work, have to close and not use the MacOS app while using Claude Code
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.