Cowork desktop: session auto-archives in <60s of inactivity (Windows)

Resolved 💬 3 comments Opened May 11, 2026 by admin431 Closed May 14, 2026

Summary

Cowork desktop is auto-archiving active sessions in less than 1 minute of no user input, forcing the user to click "Desarchivar" repeatedly to continue a single conversation. This breaks long planning/coding sessions.

Environment

  • OS: Windows 11 Home 10.0.26200
  • Cowork desktop (Spanish locale — UI shows "Esta sesión está archivada. Desarchívala para continuar la conversación.")
  • Plan: Claude Max 20 (Opus 4.7 1M context)
  • Repo: medium-sized Flutter monorepo (1,857 dart files, 147 markdown docs, 14 packages)

Observed behavior

  1. User opens a Cowork session, has back-and-forth with Claude
  2. User pauses ~1 minute to read/think (no typing, no click)
  3. Session UI flips to archived state with "Desarchivar" button
  4. User has to click "Desarchivar" to continue
  5. Repeats every <60s of inactivity

This has happened repeatedly within a single planning session (multiple times over ~2 hours).

Expected behavior

Sessions should remain active during normal reading/thinking pauses. A reasonable inactivity timeout would be 30+ minutes, not <1 minute.

Suspected cause

  • Aggressive inactivity timeout in Cowork desktop session lifecycle
  • Possible bug in MCP \ccd_session_mgmt\ archive_session trigger
  • Possible interaction with multiple parallel sessions (user reports ~131 worktrees + 40+ session entries in \~/.claude/projects/\)

Impact

User explicitly reported being "harto y cansado" (fed up). For long-form planning/architectural sessions (typical for senior engineering), this makes Cowork unusable without constant clicking.

Repro confidence

High — happens within the same session repeatedly. Reproducible on demand by pausing 60s.

Suggested mitigation

  1. Increase default inactivity timeout to 30+ minutes
  2. Expose timeout as user-configurable setting
  3. If timeout is bug (not feature), audit \mcp__ccd_session_mgmt__archive_session\ invocation conditions

Thanks. Happy to provide more logs/screenshots if useful.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗