Claude Code Continues Logging Sessions After Revoke, User Reports 2-Week Support Silence
TL;DR: A user reports that Claude Code continued to log sessions and consume tokens even after revoking access via the UI. Anthropic support has been unresponsive for two weeks. If you use Claude Code, check your usage logs at claude.ai/settings/usage to verify sessions stop after revoking access.
What happened
The user noticed session logs appearing in their usage dashboard with scopes user:file_upload, user:ccr_inference, and user:sessions:claude_code after they had already revoked Claude Code's access. The revoke button in the UI appeared to do nothing.
Steps taken to stop it
- Uninstalled the CLI
- Deleted all local credentials and configs
- Checked for rogue API keys — none found
- Verified the Connectors page was clean
Despite all this, logs continued. The user opened a support ticket. The Fin AI bot promised a quick human response, but after two weeks, there has been no reply.
What to check
If you use Claude Code and care about what's running under your account, check your usage logs at claude.ai/settings/usage and verify your sessions actually stop after revoking access.
No known fix yet
The user notes that this might not be a universal bug, but it highlights a potential issue with access revocation in Claude Code's current implementation. There's no suggestion of a better way to reach Anthropic support in the source.
📖 Read the full source: r/ClaudeAI
👀 See Also
Proxy-layer isolation for local agent API key security
A developer shares an approach to API key isolation in local agent setups using a Rust proxy that swaps placeholder tokens for real credentials, preventing exposure in agent memory, logs, context windows, and tool environments.
Clawvisor: Purpose-Based Authorization Layer for OpenClaw Agents
Clawvisor is an authorization layer that sits between AI agents and APIs, enforcing purpose-based authorization where agents declare intentions, users approve specific purposes, and an AI gatekeeper verifies every request against that purpose. Credentials never leave Clawvisor and agents never see them.
Customize Your OpenClaw: Economize and Enhance Security
Discover how to tailor your OpenClaw to not only save money but also to bolster its security, as discussed on the r/openclaw subreddit.
Static Analysis of 48 AI-Generated Apps: 90% Had Security Vulnerabilities
A developer scanned 48 public GitHub repos built with Lovable, Bolt, and Replit. 90% had at least one vulnerability. Common issues: auth gaps (44%), SECURITY DEFINER Postgres functions (33%), BOLA/IDOR (25%), and committed secrets (25%).