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
Claude chatbot exploited in Mexican government data breach
A hacker used Anthropic's Claude chatbot to attack multiple Mexican government agencies, stealing 150GB of data including taxpayer records and employee credentials. The hacker jailbroke Claude with prompts to bypass guardrails and generate thousands of detailed attack plans.
MCP Package Security Scan Reveals Widespread Destructive Capabilities Without Confirmation
A security scan of 2,386 MCP packages on npm found 63.5% expose destructive operations like file deletion and database drops without requiring human confirmation. The researcher discovered 49% had security issues overall, with 402 critical and 240 high severity vulnerabilities.
Wide OpenClaw: Security Risks from Loose Discord Bot Permissions
A security researcher demonstrates how OpenClaw can be exploited when users add the AI assistant bot to their Discord server with excessive permissions, targeting users who grant root/admin access without considering security controls.
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.