[BUG] VS Code: archiving a session creates a new "Untitled" session even when other sessions are open

Status Open
Reported on v2.1.289
Maintainer reply None cached
Activity 0 comments · opened Oct 7, 2026

Summary

In the VS Code extension, archiving the current session sometimes creates a new, empty "Untitled" session, even though other sessions are still open. I'd expect it to switch to one of the open sessions.

Environment

  • Claude Code VS Code extension 2.1.289
  • VS Code 1.141.0
  • macOS

Steps to reproduce

  1. Open two or more sessions in the Claude Code panel.
  2. Archive the session that is currently shown.

Expected

  • If other sessions are open, switch to one of them (for example the most recently used).
  • Only if the archived session was the last open one, create a new "Untitled" session.

Actual

The behavior is inconsistent. Sometimes it switches to another open session, as expected. Other times it creates a new "Untitled" session even though other sessions are open. That leaves stray empty sessions behind, and I have to go find the one I wanted.

Related

  • #97703 also concerns what the panel opens after an archive, but from the process side: the session it switches to gets resumed and starts a new claude process. This issue is about creating an "Untitled" session when it shouldn't.

View original on GitHub ↗