[Bug] Cyber Verification Program prompt repeatedly shown to already-verified account
Status Open
Reported on v2.1.248
Maintainer reply None cached
Activity 0 comments · opened Sep 25, 2026
Bug Description
My account is already approved under the Cyber Verification Program (CVP). Despite this, Claude Code repeatedly blocks or interrupts security-related tasks and prompts me to apply for cyber verification again.
Expected Behavior
Once an account is CVP-verified, Claude Code should recognise the verified status and stop showing the verification/application prompt for eligible security work.
Actual Behavior
- Security-related requests are intermittently refused or interrupted.
- The CLI repeatedly displays a prompt directing me to apply for cyber verification, even though verification is already complete.
- The issue recurs across sessions.
Steps to Reproduce
- Sign in to Claude Code with a CVP-verified account.
- Run a security / penetration-testing related task.
- Observe the prompt asking to apply for cyber verification.
Environment
- Platform: win32
- Terminal: Windows Terminal
- Claude Code version: 2.1.248
- Feedback ID: f5d1e587-9b13-4a12-8382-d43d9202e856
Errors Captured
The following error was logged in the same session (may or may not be related):
[{"error":"TelemetrySafeError: VirtualMessageList: itemKeys/messages length desync (keys=312 messages=311 range=[234,312))\n at jS (B:/~BUN/root/chunk-0ztk17ns.js:24:22792)\n at Pm (B:/~BUN/root/chunk-0ztk17ns.js:24:16104)\n at Ba (B:/~BUN/root/chunk-rtrzr3a8.js:18:20034)\n at Du (B:/~BUN/root/chunk-rtrzr3a8.js:18:38200)\n at Fh (B:/~BUN/root/chunk-rtrzr3a8.js:18:84275)\n at yg (B:/~BUN/root/chunk-rtrzr3a8.js:18:83275)\n at Ju (B:/~BUN/root/chunk-rtrzr3a8.js:18:83104)\n at wh (B:/~BUN/root/chunk-rtrzr3a8.js:18:79629)\n at Ve (B:/~BUN/root/chunk-rtrzr3a8.js:18:6260)\n at Ye (B:/~BUN/root/chunk-rtrzr3a8.js:18:4791)","timestamp":"2026-09-24T23:29:40.478Z"}]
Additional Context
Please advise whether the verified status needs to be re-linked to the Claude Code account, or whether this is a client-side check issue.