Hello;
The orderby UPDATE IS NOT WORKING when paired with the workspace grouping. I don’t think the “UPDATED” filter is working, i thought “updated” means it will come up? i have now paired repo+update and the repo is still at the old position instead of moving up.
Hi there!
We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.
To help us investigate and fix this faster, could you edit your original post to include the details from the template below?
Where does the bug appear (feature/product)?
Describe the Bug
A clear and concise description of what the bug is.
Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!
Expected Behavior
What is meant to happen here that isn’t working correctly?
Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)
Operating System
Version Information
agent about in your terminalIDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......
CLI:
CLI Version 2026.01.17-d239e66
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hey there!
This one is actually working as intended rather than a bug, but there’s a one-setting change that should get you what you’re after.
In the Agents sidebar there are two separate controls in the customize menu: Grouping and Ordering. The Ordering control (Updated / Status / Created) only sorts the sessions inside each group. It doesn’t reorder the groups themselves. So with Grouping: Repository (or Workspace), the repo headers keep a fixed order: you can drag a header to move it, and brand-new repos appear at the top, but an existing repo won’t automatically jump up just because it had recent activity.
If you want the most recently updated work to always float to the top, open the customize menu (the settings icon at the top of the Agents sidebar) and switch Grouping → Updated. That flattens everything across workspaces into recency buckets (Today / Yesterday / Last 7 Days), so your latest work stays up top. Grouping → Status works well too, since it keeps Working and Needs Attention sessions at the top regardless of repo.
Keeping repository grouping while also having the groups themselves re-sort by last activity isn’t something the sidebar does today. It’s a real gap we’ve heard before, and there’s an open feature request collecting this exact feedback if you’d like to add your use case: Agents Window sidebar for multi-repo orchestration.
If instead you’re seeing sessions within a single repo not sorting by last update, that would be a bug. A quick screenshot would help me dig in.
In the same customize menu (the funnel icon at the top of the Agents sidebar), open Show and turn on Workspace (and Branch too, if it helps). That adds the repo/workspace name as a line under each chat title, so even in the flattened Updated view every chat is clearly labeled with its project. You keep the recency ordering you wanted and can still tell projects apart at a glance.
A couple of quick ways to double-check a chat’s repo so you don’t send to the wrong one:
If what you’d really prefer is to keep the repository grouping and have the project folders themselves re-order by most recent activity (instead of flattening), that’s a genuine gap today. There’s an open request describing exactly that if you’d like to add your use case: Sort workspace folders by activity while keeping project hierarchy. We track these to gauge interest, which helps the team prioritize.
