Bug where Changes is always the default view

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Whenever the agent chat is loaded, Changes view is the default view. Why is this? And also the Changes view is not an accurate reflection oof the actual code changes in the branch / session.

Steps to Reproduce

Open new agent chat, changes will automatically be defaulted.

Expected Behavior

Chat should be the landing when new agent is selected - whether or not its a new or existing workspace.

Operating System

MacOS

Version Information

Version: 3.15.6
VS Code Extension API: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. Let’s break it down.

About the default tab being Changes: the chat itself doesn’t go anywhere. It’s a separate conversation panel. On the right editor panel, in current builds, Changes opens as the default tab, and that choice is remembered per workspace. Separately, there’s an issue where right after sending a new chat, the panel is forced to switch to Changes. That’s something we’re tracking. I can’t share a timeline yet, but I’ll post here if there’s an update.

About “it doesn’t reflect changes accurately”: the Changes tab shows a diff based on the scope you pick in the dropdown at the top:

  • Uncommitted: working tree vs HEAD
  • Branch: commits vs the merge-base with the default branch
  • Last Turn: only files touched by the agent’s last turn

So it can look different from “all changes in the branch” depending on the selected scope. Please double-check what scope you have set. If you still see a mismatch for a specific scope, please share a screenshot of the Changes tab with the scope visible and describe what exactly doesn’t match. Then we can dig deeper.