VS Code users experience inconsistent session management keybindings

“Does this issue occur when all extensions are disabled?: Yes/No VS Code Version: Version: 1.140.0 (Universal) OS Version: macOS Golden Gate 27.0 Steps to Reproduce: 1. Open command palette (i.e. Cmd + Shift + P), and type "Chat: Manage Language Models" 2. There is no delete button against the model/model group. The delete button should be there irrespective of if API keys have been enabled for that model or not. <img width="1206" height="654" alt="Image" src="https://github.com/user attachments/”

“Environment Extension: anthropic.claude code 2.1.268 running (2.1.273 / 2.1.274 / 2.1.280 staged on disk, auto installed 9/11 9/23) VS Code 1.137.0, Windows 11 Pro 10.0.26200 claudeCode.preferredLocation: "sidebar" set explicitly in settings.json Related open issues: 94499 (new sessions ignore the sidebar setting since 2.1.268), 95379 (sessions list does not reflect real state without a window reload), 96348 (cannot move Claude to editor area / second window) Summary Before 2.1.268 the Claude pa”

“Does this issue occur when all extensions are disabled?: Yes/No VS Code Version: 1.139.0 insider (4fa9fcf245ad90eb1f21fae5ed0511515e068b1d) OS Version: Windows 11 Steps to Reproduce: 1. Open the Chat sidebar and use Move Chat into New Window <img width="469" height="216" alt="Image" src="https://github.com/user attachments/assets/d0b21628 a84a 49ec a466 0e6ed25760a9" / 2. Prompt something 3. Close the chat window 4. Go to the Sessions list and see that session does not appear there 5. Restart VS”

“Description In the Claude Code VSCode extension, when opening the session list (e.g. after creating a new session), the only actions available on a session are Archive / Unarchive . There is no option to permanently delete a session. Steps to reproduce 1. Open the Claude Code VSCode extension. 2. Create a new session. 3. Try to remove an old/unwanted session from the list. 4. Only "Archive" / "Unarchive" actions are available — no "Delete". Expected behavior Users should be able to permanently d”

“Steps to reproduce 1. Open a session in the Agents Window. 2. Create an additional chat within that session. 3. Focus the new chat transcript or input. 4. Press F2 . Expected The rename prompt targets the focused chat and is populated with that chat title. Actual The rename prompt targets the owning session and is populated with the session title. Confirming the prompt renames the session instead of the focused chat. Recording Agents Window F2 rename issue”

“Does this issue occur when all extensions are disabled?: Yes VS Code Version: 1.137.0 OS Version: macOS 26.6.2 Steps to Reproduce: 1. Open the Agents window. 2. Open multiple chat tabs and terminal tabs. 3. Focus the terminal. 4. Press Cmd+Shift+[ or Cmd+Shift+] . The active chat changes instead of the terminal tab. 332029 removed these shortcuts from session navigation. Chat navigation still uses them.”

“Steps to reproduce 1. Open an existing chat session as a Chat Editor. 2. Focus the chat editor. 3. Press Ctrl+N. Actual behavior The existing editor is cleared and replaced with a blank new chat. The old session is no longer open as an editor. Expected behavior The existing session editor remains open, and Ctrl+N opens a separate new Chat Editor. Technical details Both workbench.action.chat.newChat and workbench.action.openChat are bound to Ctrl+N in a chat editor. The former has the higher keyb”

“Problem Chat session management keybindings are inconsistent across chat surfaces: The existing session Rename command is available from the sessions UI, but its keybinding does not work when focus is in the panel/editor chat transcript or input. The Agents Window exposes Rename and Delete actions without equivalent list/chat keybindings. Rename must follow the active session's actual capability. Unsupported contributed sessions (for example, cloud sessions) and provisional Agent Host sessions b”

“Problem Restoring several persisted multi root Copilot CLI sessions can trigger enough concurrent Agent Host Git work that background branch summary probes hit the hard 5 second timeout. Repositories whose probe times out are omitted from the all folder changes summary. This was observed in recent Code Insiders 1.135.0 insider sessions with trace logging enabled. Exact timeout counts: 20260825T095440/agenthost.4.log : 61 occurrences of timed out after 5000ms 20260825T161812/agenthost.3.log : 5 o”

“Does this issue occur when all extensions are disabled?: Yes VS Code Version: 1.134.0 (110a328ea54b42367b803ec53ee0bf52ef26b419, arm64) OS Version: macOS 26.6.1 (25G76) Steps to Reproduce: 1. Open a local folder in VS Code so that it appears under File Open Recent. 2. Close the folder's VS Code window, then delete the folder in Finder. 3. From the macOS menu bar, select File Open Recent and choose the deleted folder. 4. When the “Path does not exist” dialog appears, select OK. 5. Open File Open”

“Description I have both a vscode docs and vscode docs pr repo. When I create a session from a PR, the repo for the PR list is inverted. When I create a session for vscode docs, the PR for vscode docs pr are shown, and vice versa. Issue Details Item|Value | Issue Category|Bug Target|Agents Window VS Code Version|Code Insiders 1.135.0 insider (68953c79d41be497c119c6602fd85158a5ee56b8, 2026 08 25T00:12:38Z) OS Version|Windows NT x64 10.0.26200 <details <summary System Info</summary Item|Value | VS”

“The Agents window sessions picker was bound to Ctrl+R on macOS, which clashed with VS Code's own "Open Recent" (recent workspaces) shortcut. Fixed by 325689: macOS Ctrl+R stays available for opening recent workspaces. The sessions picker moves to macOS Ctrl+Alt+R . Sticky forward/backward picker navigation uses Ctrl+Alt+R and Ctrl+Alt+Shift+R . Verification steps (macOS) 1. In the Agents window, press Ctrl+R → ✅ it opens recent workspaces (not the sessions picker). 2. Press Ctrl+Alt+R → ✅ the se”

“Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after bug verification. Leveraging Agency Copilot can help accelerate this accessibility bug fix; review and validate all AI generated changes before merge. "Check out Accessibility Insights! Identify accessibility bugs before check in and make bug fixing faster and easier." GitHub Tags A11yTCS; Visual Studio Code Client; agency:plugin=a11y@company; E2E VisualStudioCodeClient Win32 Dec2025; DesktopApp;”

“Ported from https://github.com/microsoft/vscode/issues/298507 I see that if I start with one folder open, and add a folder to the workspace, that turns it from a single folder to a multi root workspace, and then I see my chat entries in history but clicking fails to open them. Does that sound like your problem? The reason for that is that it's technically a different workspace when you switch to the multi root window, and chats are stored per workspace, but it looks like the chat index gets copi”