Describe the Bug
Summary
The “Default Location” setting in Cursor’s Agent settings (set to “Editor”) does not work. Agent sessions still open in the Agent Pane instead of editor tabs, despite the setting being configured correctly in the UI.
Environment
- OS: Windows 10 (Build 26200)
- Cursor Version: [Please fill in your version - Help > About]
- Settings Location:
C:\Users\[username]\AppData\Roaming\Cursor\User\settings.json
Additional Issues
- The manual “Open in Editor” option (three-dot menu) also does not work
- This worked previously (user could manually move chats to editor pane), but no longer functions
Workaround
The Ctrl+L command (aichat.newchataction) does work to move agent sessions to editor tabs:
- Start agent session normally
- Press
Ctrl+L - Session moves to editor tab and continues working normally
This confirms the underlying functionality exists, but the default behavior and UI menu options are broken.
Settings Attempted
Tried multiple setting variations in settings.json (none work):
cursor.agent.defaultLocation: "Editor"cursor.agent.location: "editor"cursor.chat.defaultLocation: "Editor"cursor.agent.openInEditorTab: true
Impact
- Users cannot set agent sessions to open in editor tabs by default
- Manual workaround required (
Ctrl+L) for each session - Degrades user experience and workflow efficiency
Related
- Similar issue reported: “Cursor: Open Chat” command not working (forum posts from 2024)
- This appears to be a regression or related bug affecting the same functionality
Steps to Reproduce
- Open Cursor Settings (
Ctrl+Shift+JorCursor > Settings > Cursor Settings) - Navigate to Agents section
- Set Default Location dropdown to “Editor”
- Start a new agent session (via any method:
Ctrl+I, Command Palette, etc.) - Observed: Agent session opens in the Agent Pane (right sidebar)
- Expected: Agent session should open in an editor tab
Operating System
Windows 10/11
Version Information
Version: 2.4.21 (user setup)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Does this stop you from using Cursor
No - Cursor works, but with this issue