[BUG] Sessions are auto-archived immediately after Claude sends a message

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?

Sessions in Claude Code Desktop App (Windows) are being automatically archived immediately — even right after Claude sends a response in the chat. This happens repeatedly during active use, forcing the user to search for and unarchive the session every time they want to continue a conversation.

This is extremely disruptive. The session disappears while the user is actively using it, not after any extended period of inactivity.

What Should Happen?

Sessions should remain active and accessible during ongoing use. Auto-archiving should only occur after a long and genuine period of inactivity (e.g., several hours or days), not immediately after Claude sends a response.

Error Messages/Logs

Steps to Reproduce

1. Open Claude Code Desktop App (Windows)
2. Start a conversation with Claude
3. Wait for Claude to send a response
4. Session is immediately archived — sometimes within seconds of Claude's response appearing
5. The session disappears from the active list; user must search to find and unarchive it

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.167 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Using Claude Code Desktop App on Windows 11 Pro (10.0.26100). The session archiving occurs extremely frequently — even immediately after Claude sends a response in the active chat window. There is no configuration in settings.json to disable or adjust auto-archiving behavior, leaving the user with no workaround other than manually searching for and unarchiving the session each time.