VS Code 1.123 Syncs Agent Sessions to GitHub and Adds a /chronicle Command, Pushing the Editor Toward Persistent AI Workflows
The June 3 release adds cross-machine chat session sync, a Research Agent preview, 1M-token context windows, and a two-hour delay on extension updates.
Overview
Microsoft shipped version 1.123 of Visual Studio Code on June 3, a release that, in the words of the official notes, “improves how you work with agents and the integrated browser,” according to the VS Code release notes. The update leans heavily into keeping long-running AI agent work coherent across sessions and machines: chat history now syncs to a developer’s GitHub account, a new command lets users query that history in plain language, and an experimental Research Agent generates cited Markdown reports. The corresponding build is tagged 1.123.0 in the project’s GitHub releases.
The release arrives roughly six weeks after VS Code 1.121, which introduced remote agents over SSH and a new open agent protocol. Where that update focused on where agents run, 1.123 concentrates on persistence — making an agent’s accumulated context survive across days and devices.
What We Know
Chat sessions now sync to GitHub. According to the VS Code release notes, “Your chat sessions now sync automatically to your GitHub account, giving you a personal, searchable history of your work across machines and workspaces.” The stated goal is to make a developer’s accumulated chat context portable rather than tied to a single machine or workspace.
A new /chronicle command queries that history. The release notes list its capabilities as the ability to “Ask natural-language questions about past sessions,” “Generate standup reports,” “Get personalized productivity tips,” and “Search your coding history by topic, file, or PR,” per the VS Code release notes. The command turns the synced session history into a queryable record rather than a passive archive.
A Research Agent enters preview. Marked “(Preview)” in the release, it produces “a thorough, well-cited Markdown report by gathering and synthesizing information from your codebase, relevant GitHub repositories, and the web,” according to the VS Code release notes.
Multiple agent sessions can run at once. The release notes state, “You can now have more than one session open at the same time in the Agents window,” per the VS Code release notes — letting developers run and compare parallel agent runs from a single view.
Context windows expand to one million tokens. “VS Code now supports 1 million token context windows for compatible Anthropic and OpenAI models,” the VS Code release notes state, adding that the expanded window is available “when using supported models, such as Claude Opus 4.7 and GPT-5.5.”
Extension auto-updates now wait two hours. “VS Code now applies a two-hour delay before automatically updating extensions to a newly published version,” according to the VS Code release notes. The delay is positioned as a buffer against problematic or compromised releases reaching users immediately.
The integrated browser gains favorites and screenshot context. Users can now add a page to their favorites by selecting “the star icon in the browser URL bar,” and two new screenshot actions — “Add Area Screenshot to Chat” and “Add Full Page Screenshot to Chat,” the latter marked Experimental — let developers capture an interface and pass it as chat context, per the VS Code release notes.
What We Don’t Know
The release notes do not specify which additional Anthropic and OpenAI models, beyond Claude Opus 4.7 and GPT-5.5, qualify as “compatible” for the one-million-token context window, nor whether third-party providers are supported. The Research Agent remains a preview feature, and Microsoft has not stated when it will reach general availability. Microsoft also has not published adoption or performance figures for the new session-sync infrastructure.
Analysis
The throughline of 1.123 is persistence. Earlier VS Code releases focused on expanding where and how agents execute; this one is concerned with what happens to an agent’s context between runs. Syncing chat history to a GitHub account, making that history queryable through /chronicle, and pushing context windows to a million tokens all point in the same direction — treating an AI coding session less like a disposable chat and more like a durable, searchable record of work. The two-hour delay on extension auto-updates, meanwhile, is a measured response to the supply-chain risk that has repeatedly surfaced in the editor’s marketplace, trading immediate updates for a short window in which a compromised release can be caught.