[BUG] "New session" returns to an existing session instead of creating a new one

Status Open
Maintainer reply None cached
Activity 0 comments · opened Jul 16, 2026

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?

Clicking "+ New session" (Code tab) does not start a fresh session. Instead, it returns to an
existing session already in my Recents list. I confirmed this by clicking a different session,
then clicking back — it returned to the same existing session both times, not a new one. Tried
this twice, same result both times.

Separately: that existing session shows a status of "Needs input" on the Home tab, with the
one-line preview "awaiting user to retry in new session" — even though the session itself is
active and working normally when I open it. Not sure if that status label is related to this bug
or a separate display issue.

What Should Happen?

Clicking "New session" should create a genuinely new, empty session — not return to an existing
one already in the Recents list.

Error Messages/Logs

Steps to Reproduce

  1. Have at least one existing session already open in Recents for a given folder
  2. Click "+ New session" (Code tab), pointed at that same folder
  3. Result: instead of a fresh session, it returns to an existing session already in Recents
  4. Confirmed by clicking a different session in Recents, then clicking back — returned to the

same existing session both times, not a new one

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Unable to determine — claude --version not available in this environment.

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

Related to a separate report I filed (issue #78297) about the same "AI Class" project folder,
but this is a distinct bug from that one.

View original on GitHub ↗