Agents view missing features / UI from editor view

TLDR; I loved the new Agents view, but transitioning from Editor view to Agents still is no as smooth as it should be.

Customizability is the main pain point here.

Here’s whats missing:

  1. Git panel (Source Control).
    • List view for changed files (currently only tree view).

    • When showing Uncommitted changes filter, show a split view for unstaged & staged changes (like in editor mode).

  2. Allow customizable shortcuts or map them from editor mode (e.g., Cmd + Shift + E for files).
  3. Allow showing only one agent chat in the chat side panel. (Currently 2 is the minimum):
  4. Ability to run VScode tasks (e.g., I have some terminal commands that run by triggering a task).
  5. Probably a far reach, but themes & icon packs from editor view would be very useful for readability (e.g., Material Icons).

Is there any plan to implement any of this or add more customization ?

Hey, thanks for the feedback. A well-structured list really helps with prioritization.

Point by point:

  1. Git panel list view and staged/unstaged split
    Right now, Glass only has a tree view. The team knows Source Control needs improvements. There are already a few similar requests, like this thread about a native commit and push UI: Use native code changes view/commit and push view instead of asking the AI in Agent Mode

  2. Customizable shortcuts
    Also on the radar. There’s a separate feature request for the same thing. Feel free to add your vote there: Agents Window: Customize keybindings

  3. Single agent chat
    I’ll flag this for the team. No workaround yet.

  4. VSCode tasks
    Not supported in Glass yet. If you need VSCode tasks, you can switch to classic mode.

  5. Themes and icon packs
    This is being actively worked on, including syncing the theme between Glass and the editor view. For now, it’s light and dark only.

Agents Window is still early, and customization is a big focus. This post covers many of the same points: Cursor 3.0 Agentic IDE – Huge Potential, but Blocked by Key Usability Gaps
For tasks where these limits get in the way, classic mode is still the reliable option.

Thanks for the reply! Good to know it’s in progress.
Good luck to you guys.