Fixed / manual order for pinned chats (don't re-sort on activity)

Feature request for product/service

Cursor IDE

Describe the request

Feature request for product/service

Chat / Agents sidebar

Describe the request

Problem

Pinned chats stay in the “Pinned” section at the top (Cursor 2.2+), which is great — but the order within the pinned section is not stable.

When I pin chats to specific positions (e.g. position 1 = ongoing project, position 2 = PR review), writing in a pinned chat moves it to the top of the pinned list. The pin keeps it above unpinned history, but it does not keep it at the slot I chose.

This makes pinning much less useful for workflows where each pinned chat has a fixed role, not a “most recently used” priority.

Current behavior

  • Pinned chats appear in a “Pinned” block above normal history :white_check_mark:
  • Order within “Pinned” appears to follow last activity (recently used chat jumps to top)
  • No setting to lock order
  • No drag-and-drop to reorder pinned items
  • No “sort pinned by: Manual | Last active | Created” option

Expected behavior

When I pin a chat, its position in the pinned list should stay fixed until I manually change it.

Example:

  • Pin chat A → position 1
  • Pin chat B → position 2
  • Write in chat B → chat B stays at position 2, does not jump above chat A

Proposed solution

Option A (minimal): Pinned order = order pinned (first pinned = top). Activity does not reorder pinned items.

Option B (flexible): Add sort toggle for pinned section:
Pinned sort: [Manual | Last active | Created]

Option C (full): Drag-and-drop reorder in the pinned section + optional lock per chat.

Use case

  • Pin 1: long-running project chat
  • Pin 2: current PR / code review
  • Pin 3: experiment / spike

I switch between them often. I want muscle memory — always the same visual order — not “whoever I last messaged is now #1”.

Related

Operating System

macOS

Thank you for considering this!

Indeed, fixed or locked chat historic should be considered needed, tho as you may be aware, keeping the same chat active isn’t actually a good setup nowedays considering how context work, and I guess that’s the reason why the team hasn’t implemented this feature yet.