[Web/Desktop UI] Active session auto-archived every ~5 minutes during normal interaction

Bug: Active session auto-archived every ~5 minutes during normal interaction

Summary

The web/desktop client of Claude Code is automatically archiving sessions that are actively in use (human messages incoming and agent producing output). The "Esta sessão está arquivada / Desarquive-a para continuar a conversa" banner appears every 5 minutes or less, forcing the user to click "Desarquivar" before every new message.

Expected behavior

According to the docs, only background sessions with no actionable output for 5 minutes should be auto-archived. Sessions with active human-agent interaction should remain live indefinitely.

Actual behavior

A session with continuous interaction over 24+ hours (multiple commits, file edits, Bash commands, browser automation, deploys) is being archived every ~5 minutes, regardless of:

• Frequency of user messages (under 5min apart)
• Recency of agent output (tool calls completing continuously)
• Whether the user is actively reading the response on screen

Reproduction

100% reproducible:

1. Open Claude Code via web/desktop UI (not CLI)
2. Start any session with active interaction
3. Send messages and receive agent responses for ~5 minutes
4. Banner appears: "Esta sessão está arquivada. Desarquive-a para continuar a conversa."
5. User clicks "Desarquivar"
6. Conversation resumes, then archives again within ~5 minutes

Diagnostic steps already exhausted by the user

• ✅ Uninstalled the Claude mobile app — issue persists
• ✅ Disabled Remote Control feature — issue persists
• ✅ Signed out of all devices via claude.ai/settings → Sign out of all sessions — issue persists
• ✅ Verified no extensions interfering (Dark Reader / similar tested via incognito) — issue persists
• ❌ No hooks configured in ~/.claude/settings.json (only theme: auto, agentPushNotifEnabled: true, inputNeededNotifEnabled: true)
• ❌ No project-level .claude/settings.json exists

Confirmation that this is NOT agent-triggered

The agent (Claude itself, in the affected session) verified its own tool call history and never invoked mcp__ccd_session_mgmt__archive_session during the session. The deferred tool exists in the infrastructure but is not being called by the agent. This indicates the auto-archive is happening server-side or client-side, outside of agent action.

Environment

• OS: Windows 10 Pro 10.0.19045
• Client: Claude Code web/desktop UI
• Model: Claude Opus 4.7 (1M context)
• Session length when archive occurs: Variable, sometimes 30 seconds after "Desarquivar", typically within ~5 minutes
• Activity profile: High — frequent file edits, Bash, browser automation, Firebase deploys

Impact

• Severe UX disruption: user has to click "Desarquivar" before each message after the first archive
• Loss of trust in product
• Forces migration to CLI as only viable workaround

Suggested fixes

• Treat sessions with any human message OR agent tool call in the last N minutes as "active" and exempt from auto-archive
• OR: expose a setting in claude.ai/settings to disable auto-archive for active users
• OR: warn the user before archiving so they can postpone

Additional context

This report was generated by the agent inside the affected session, after the user explicitly requested help diagnosing the issue. The session itself was archived at least 8 times during the diagnostic conversation.

Related issues

• #30869, #41303, #43304 (one-way archiving limitation — no unarchive feature)