Pinned sessions reorder themselves; messages get routed to the wrong session

Status Open
Reported on v2.1.100
Maintainer reply None cached
Activity 0 comments · opened Jul 22, 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?

I work with 5-6 long-running sessions open at the same time, one per project. The sidebar list keeps reordering itself constantly - including sessions I have explicitly pinned. Pinning does not hold the position.

Real example from today, same 4 rows, minutes apart:

Before:

  1. PP
  2. Paking listy
  3. 5min
  4. ReloMonitor

After (nothing was moved by me):

  1. 5min
  2. Paking listy
  3. PP
  4. ReloMonitor

Because the rows rotate, I click what I believe is session X, type there, and the message goes to a different session. The answer comes back with the context of an unrelated project. This is the worst possible failure mode for multi-session work - I lose track of which project I am even talking to, and wrong context leaks into wrong sessions.

What Should Happen?

A pinned session stays at the same position until I unpin it or move it myself.
The list must not reorder while I am reading or clicking it.

Error Messages/Logs

No error message - the list simply reorders silently.

Steps to Reproduce

  1. Open several long-running sessions in the sidebar (in my case 6, across different projects).
  2. Pin some of them.
  3. Work in one session for a while, then look at the sidebar again.
  4. The pinned sessions have swapped positions with each other and with unpinned ones - the list appears to re-sort by recent activity, overriding the pin.
  5. Click the row where a given session used to be and send a message: it lands in a different session and the assistant answers with context from an unrelated project.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.100 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

This is not cosmetic. Work gets written into the wrong session's history and the assistant answers using context from another project. With 5-6 long-running projects open, the sidebar is unusable as a way to target a specific session - the only reliable identifier is the session name in the header, never its position.

I have been hitting this daily for weeks. If pinned sessions cannot stay put, multi-session work is not viable for me and I will have to stop using Claude Code for it.

Suggested fix:

  • Pinned sessions get a fixed order that activity never changes.
  • Freeze the list order while the pointer is over the sidebar, so a click cannot land on a row that moved between hover and click.
  • If reordering is intentional, make it opt-in (a sort toggle), not the default.

---

Why I think this is a design decision, not just a glitch

The rule "the session with the newest reply jumps to the top" is the single worst idea here. I am not browsing a feed - I am working in parallel on 6 fixed projects. Their order should be whatever I set it to, permanently. Re-sorting them by activity is not a feature, it is a bug in disguise.

Six sessions is not a lot to remember. The app rotates them as if it could not hold six positions in memory. There is no scenario in which I benefit from that.

Pinning is currently pointless. There is even a Shift option to move a session up or down - so the app clearly accepts that I want a specific order - and yet after a while the pinned sessions rearrange themselves anyway. A pin that does not pin is worse than no pin at all, because it makes me trust a position that is about to change.

The practical damage: the list misleads me, I send a prompt into the wrong session, and work lands in the wrong project's history with the wrong context. This is the worst-functioning part of the product for me, hands down.

What I need is simple: the order I set stays until I change it. No activity-based re-sorting, ever - or at most an opt-in toggle that is off by default.

View original on GitHub ↗