GitHub Copilot in VS Code v1.135

GitHub Copilot in VS Code v1.135 was released on .

Summary

Agents Agent host The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The...

Release Context

Shipped around the same time

Within 3 days of this release, other AI coding tools also shipped:

Compare GitHub Copilot in VS Code

Release Notes

Agents Agent host The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK, which aligns the agent's behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products. We're actively developing the agent host. The following screenshot shows the Copilot harness selec... Continue external agent sessions in VS Code Setting: setting(chat.agentSessions.showExternal) The Sessions list in VS Code can now show recent Copilot or Claude agent sessions that you created in other applications. By default, VS Code shows up to two recently updated external sessions. Select a session from the Sessions list to view the conversation and continue it in VS Code with your Copilot subscription. When you open an external session, a banner at the top of the chat lets you configure how many external sessions appear in the Sessions list. You can also use the Externa... Rubber Duck (Experimental) Rubber Duck is an experimental feature that allows you to get a second opinion from a complementary model on the agent's work. It helps surface missed details or edge cases. You can use Rubber Duck by invoking the /rubber-duck command in a Copilot agent host session. Learn more about Rubber Duck in GitHub Copilot CLI. Single-pane side layout is now the default Setting: setting(sessions.layout.singlePaneDetailPanel) In the previous release, we introduced the single-pane layout. In this layout, session details and editors are located in a single side pane, with a shared tab bar next to chat. The single-pane layout is now enabled by default for the Agents window on desktop. This release also improves the layout: Diffs use a side-by-side view when space permits and switch to an inline view when the side pane becomes too narrow. Use Always Show Inline Diff from the editor title menu to kee... Simplified session controls and information The session header is less crowded, so you can identify the active session more easily and focus on the conversation. The session title has a prominent position, while an overflow menu next to the title groups actions for creating a chat and pinning the session. Search remains available in the Sessions list. When a session contains multiple chats, chat tabs replace the single-chat header. Session information moves directly above the chat input, where it is easier to find while you work. Pills can show changes, pull requests, issues, browser... Chat Editor-style sticky scroll for chat (Experimental) Settings: setting(chat.stickyScroll.enabled), setting(chat.experimental.stickyScroll.enabled) Chat sticky scroll lets you keep the current prompt visible as you scroll through and review long responses. We've further refined the behavior to make it more consistent with sticky scroll in the editor. Enable both settings to try the redesigned experience. View detailed chat turn usage To give you better insight into your chat usage, we've redesigned the chat response footer. When you hover over it, the footer shows a per-model breakdown of the input, cached input, and output tokens used in that chat turn. Sandboxing for the local agent harness We previously rolled out sandboxing to 50% of users to validate it on a larger scale and in real-world use cases. While we didn't identify a specific blocking issue, continuing the rollout would likely require more support and follow-up work at a time when we want to preserve focus on higher-priority investments, especially in the area of the agent host and the Copilot harness. We've therefore returned the default rollout to 0% for now. Sandboxing for the local agent harness remains available as an opt-in feature through the UI, so users who want...

View original release

Other Recent GitHub Copilot in VS Code Releases

Upgrading from v1.135? See all 7 releases since.

All GitHub Copilot in VS Code releases · All AI coding tool releases on Havoptic