claude-code [CRITICAL BUG] Claude Code Web: Archived sessions reappear as ACTIVE RUNNING sessions, potentially consuming tokens

Preflight Checklist

[x] I have searched existing issues and this hasn't been reported yet
[x] This is a single bug report (please file separate reports for different bugs)
[x] I am using the latest version of Claude Code

What's Wrong?

CRITICAL: When I archive sessions in Claude Code Web and then navigate away (e.g., to a regular Claude chat) and return to Claude Code, all my archived sessions immediately reappear in the "Active" sessions list. More critically, dozens of these sessions display the pulsing Claude logo indicator, making them appear as if they are actively running and potentially consuming tokens/usage credits. The issue reproduces 100% of the time with these steps:

Archive sessions in Claude Code Web Navigate to claude.ai (regular chat) Navigate back to claude.ai/code All archived sessions are back in the "Active" list Many show the pulsing indicator as if actively running

This makes the archive feature completely non-functional and raises serious concerns about unauthorized resource consumption.

What Should Happen?

Expected Behavior When sessions are manually archived:

They should move from the "Active" list to the "Archived" list They should remain in the "Archived" list permanently unless manually unarchived The "Active" filter should only show sessions that have not been archived Archived sessions should NOT be running or consuming resources Only genuinely active sessions should display the pulsing Claude logo indicator

Error Messages/Logs

main.js:1 Object
main.js:1 Object
92351-828eef565a78936a.js:13 undefined
87c73c54-41cd93e91d16f29c.js:1 Uncaught Error: Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
    at rD (87c73c54-41cd93e91d16f29c.js:1:35816)
    at oq (87c73c54-41cd93e91d16f29c.js:1:85320)
    at ik (87c73c54-41cd93e91d16f29c.js:1:115436)
    at 87c73c54-41cd93e91d16f29c.js:1:115281
    at ib (87c73c54-41cd93e91d16f29c.js:1:115289)
    at iu (87c73c54-41cd93e91d16f29c.js:1:111591)
    at iG (87c73c54-41cd93e91d16f29c.js:1:133809)
    at iW (87c73c54-41cd93e91d16f29c.js:1:132020)
    at iN (87c73c54-41cd93e91d16f29c.js:1:129705)
    at iz (87c73c54-41cd93e91d16f29c.js:1:127457)
    at ii (87c73c54-41cd93e91d16f29c.js:1:113562)
    at iu (87c73c54-41cd93e91d16f29c.js:1:112915)
    at iX (87c73c54-41cd93e91d16f29c.js:1:133688)
    at MessagePort.j (92351-828eef565a78936a.js:18:45228)
92351-828eef565a78936a.js:13 [SERVICE_WORKER] Found 1 service worker(s), which are no longer used. Unregistering.
(anonymous) @ 92351-828eef565a78936a.js:13
/sentry?o=1158394&p=4504646202490880:1  Failed to load resource: the server responded with a status of 429 ()
frame-modern.c4baac18.js:1 [Intercom] Launcher is disabled in settings or current page does not match display conditions
analytics.min.js:1 Connecting to 'https://a-api.anthropic.com/v1/m' violates the following Content Security Policy directive: "connect-src 'self' https://api.segment.io https://*.segment.io https://*.segment.com https://a-cdn.anthropic.com https://*.google.com https://*.facebook.com https://*.facebook.net https://*.doubleclick.net". The action has been blocked.
o @ analytics.min.js:1
setTimeout
l @ remote-metrics.ts:87
t @ remote-metrics.ts:89
e.initRemoteMetrics @ index.ts:8
(anonymous) @ index.ts:294
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
s @ tslib.es6.js:73
Promise.then
a @ tslib.es6.js:76
(anonymous) @ tslib.es6.js:76
u @ tslib.es6.js:72
re @ index.ts:239
(anonymous) @ index.ts:338
Promise.then
(anonymous) @ index.ts:339
t @ index.ts:307
n @ index.ts:337
n.load @ index.ts:389
n.standalone @ index.ts:393
(anonymous) @ standalone-analytics.ts:53
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
(anonymous) @ tslib.es6.js:80
u @ tslib.es6.js:72
se @ standalone-analytics.ts:49
(anonymous) @ standalone.ts:69
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
(anonymous) @ tslib.es6.js:80
u @ tslib.es6.js:72
de @ analytics.min.js:1
(anonymous) @ analytics.min.js:1
(anonymous) @ analytics.min.js:1
(anonymous) @ analytics.min.js:1
analytics.min.js:1 Fetch API cannot load https://a-api.anthropic.com/v1/m. Refused to connect because it violates the document's Content Security Policy.
o @ analytics.min.js:1
setTimeout
l @ remote-metrics.ts:87
t @ remote-metrics.ts:89
e.initRemoteMetrics @ index.ts:8
(anonymous) @ index.ts:294
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
s @ tslib.es6.js:73
Promise.then
a @ tslib.es6.js:76
(anonymous) @ tslib.es6.js:76
u @ tslib.es6.js:72
re @ index.ts:239
(anonymous) @ index.ts:338
Promise.then
(anonymous) @ index.ts:339
t @ index.ts:307
n @ index.ts:337
n.load @ index.ts:389
n.standalone @ index.ts:393
(anonymous) @ standalone-analytics.ts:53
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
(anonymous) @ tslib.es6.js:80
u @ tslib.es6.js:72
se @ standalone-analytics.ts:49
(anonymous) @ standalone.ts:69
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
(anonymous) @ tslib.es6.js:80
u @ tslib.es6.js:72
de @ analytics.min.js:1
(anonymous) @ analytics.min.js:1
(anonymous) @ analytics.min.js:1
(anonymous) @ analytics.min.js:1
remote-metrics.ts:53 Error sending segment performance metrics TypeError: Failed to fetch. Refused to connect because it violates the document's Content Security Policy.
    at o (analytics.min.js:1:23763)
    at t.<anonymous> (remote-metrics.ts:138:12)
    at tslib.es6.js:103:23
    at Object.next (tslib.es6.js:108:37)
    at tslib.es6.js:80:8
    at new Promise (<anonymous>)
    at u (tslib.es6.js:72:27)
    at t.send (analytics.min.js:1:22021)
    at t.<anonymous> (remote-metrics.ts:125:16)
    at tslib.es6.js:103:23
a @ remote-metrics.ts:53
Promise.catch
(anonymous) @ remote-metrics.ts:125
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
(anonymous) @ tslib.es6.js:80
u @ tslib.es6.js:72
t.flush @ analytics.min.js:1
l @ remote-metrics.ts:83
setTimeout
l @ remote-metrics.ts:87
t @ remote-metrics.ts:89
e.initRemoteMetrics @ index.ts:8
(anonymous) @ index.ts:294
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
s @ tslib.es6.js:73
Promise.then
a @ tslib.es6.js:76
(anonymous) @ tslib.es6.js:76
u @ tslib.es6.js:72
re @ index.ts:239
(anonymous) @ index.ts:338
Promise.then
(anonymous) @ index.ts:339
t @ index.ts:307
n @ index.ts:337
n.load @ index.ts:389
n.standalone @ index.ts:393
(anonymous) @ standalone-analytics.ts:53
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
(anonymous) @ tslib.es6.js:80
u @ tslib.es6.js:72
se @ standalone-analytics.ts:49
(anonymous) @ standalone.ts:69
(anonymous) @ tslib.es6.js:103
(anonymous) @ tslib.es6.js:108
(anonymous) @ tslib.es6.js:80
u @ tslib.es6.js:72
de @ analytics.min.js:1
(anonymous) @ analytics.min.js:1
(anonymous) @ analytics.min.js:1
(anonymous) @ analytics.min.js:1
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.
Event handler of <some> event must be added on the initial evaluation of worker script.

Steps to Reproduce

Open Claude Code Web (claude.ai/code) Navigate to the sessions list Filter to show "Active" sessions Observe old sessions that should be archived appearing in the Active list Manually archive these sessions by flagging them as archived Verify they appear in the "Archived" list and are removed from "Active" list Navigate away from Claude Code (e.g., click to go to a normal Claude chat at claude.ai) Navigate back to Claude Code Web (claude.ai/code) Check the "Active" sessions list Observe: The previously archived sessions have immediately reappeared in the Active list CRITICAL Observe: Many sessions (dozens) show the pulsing Claude logo, appearing to be actively running

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.0.50 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Dec 08 '25 19:12 Mharbulous

After 23 minutes, reset

Dec 08 '25 20:12 Mharbulous

OK, I did a little bit of intentional usage, just to get a better sense of how fast tokens get used when intentionally using them.

Dec 08 '25 20:12 Mharbulous

Fortunately, it does not seem to be using actual token credits.... at least, not when my browser is closed.

Dec 09 '25 00:12 Mharbulous

Those sessions aren't using tokens. A fix will be in for this soon, sorry!

Dec 09 '25 06:12 amorriscode

This is happening to me across web, desktop app, and the iOS app. Chats are no longer archiving. Ones that have been archived for a long time now show as idle or in progress. It's tricky to keep track of chats with the filters not working. Let me know if you need more info.

Dec 10 '25 12:12 bshanz

@bshanz Yup, according to above there is already a fix for this: https://github.com/anthropics/claude-code/issues/13402#issuecomment-3630605498

I think they must just do a slow rollout of changes so they can spot if it the fix causes even bigger issues before rolling it out to everybody.

Dec 10 '25 14:12 gerrywastaken

The fix was rolled out for this. Apologies for the delay here!

Dec 10 '25 19:12 amorriscode

👍 Confirmed. Thanks for the fix amorriscode

Dec 10 '25 22:12 gerrywastaken

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.

Dec 18 '25 14:12 github-actions[bot]