Skip to main content

Visual Studio Code 1.123 Brings Deeper AI Integration and Smarter Agent Tools

Microsoft released Visual Studio Code 1.123 on June 3, expanding its AI-assisted development capabilities with features that reflect the editor’s direction: toward a more agentic, context-aware workflow.

The update is relatively focused, but several additions stand out to developers who rely on Copilot and other AI models day to day.

A Million-Token Context Window

One of the headline changes is support for 1-million-token context windows for compatible models from Anthropic and OpenAI, including Claude Opus 4.7 and GPT-5.5. That’s a meaningful jump. Larger context lets you work with larger codebases and longer conversations without the model losing track of what came before.

There’s a trade-off. Microsoft notes that larger context windows consume more tokens per interaction, which matters for teams on usage-based billing. But for developers working on complex projects, the ability to keep more code in context without manual truncation is a practical productivity gain.

Session Sync and Chronicle

VS Code 1.123 adds session sync, which automatically backs up your chat sessions to GitHub. Sessions capture conversation history, files touched, repository context — including branch and timestamps — and referenced pull requests, issues, and commits.

The companion feature is Chronicle, accessed via /chronicle in chat. It lets developers query their session history in natural language, generate standup reports, search past work by topic or file, and get productivity suggestions based on coding patterns. For engineers who context-switch frequently or manage multiple projects, having a searchable record of past AI-assisted work could save real time.

Agents’ Window Goes Parallel

The Agents window — a companion interface for running and reviewing agent sessions — now supports multiple open sessions side by side. Developers can open sessions next to each other by dragging from the session list or using Alt+click. One session is always “active” at a time, meaning the Terminal, Files, and Changes views reflect that session’s state.

Sessions can be pinned to prevent them from being replaced when selecting others. A maximize action expands any session to full width without closing others. The feature is still in preview, but it addresses a real workflow gap: the ability to compare two agent runs or review completed work while running a new one.

Research Agent

Also in preview — and currently limited to Copilot CLI sessions in Insiders — is the research agent. Triggered via /research in chat, it performs deep research on a topic by pulling from the codebase, relevant GitHub repositories, and the web, then produces a cited Markdown report. It’s read-only by design, so it investigates without modifying code.

This is aimed at cases where a quick chat response isn’t enough — understanding an unfamiliar library, comparing implementation approaches, or learning how a specific API behaves in context.

Integrated Browser Updates

The integrated browser gets a small but useful update: you can now favorite pages and access them quickly from a redesigned URL bar that also shows open tabs. On the screenshot side, two new options complement the existing Add Screenshot to Chat feature — area screenshots and full-page screenshots (the latter is experimental and requires enabling a setting).

A Small But Useful Safety Net

VS Code 1.123 also adds a two-hour delay before automatically applying extension updates. The intent is to provide a buffer against problematic or potentially compromised releases. Extensions from Microsoft, GitHub, and OpenAI are exempt from the delay and still update immediately. You can still trigger an immediate manual update at any time.

What It Adds Up To

The session sync feature, in particular, signals something larger than just a productivity feature. Mitch Ashley, VP and Practice Lead for Software Lifecycle Engineering and AI-Native Software Engineering at The Futurum Group, sees it as foundational infrastructure for teams running agentic workflows.

“Capturing the conversation, files touched, and repository context behind each agent session turns the editor into a system of record for how software gets built,” Ashley said. “The development process becomes observable, and the reasoning behind a change becomes recoverable. That record is verification infrastructure. Teams adopting agentic coding can govern and audit agent output only to the degree they can reconstruct how it was produced, so the provenance of a change is becoming as important as the change itself.”

Taken together, VS Code 1.123 continues a clear pattern: Microsoft is embedding AI more deeply into the core development workflow rather than treating it as an add-on. Developers who spend significant time in VS Code with Copilot enabled will find practical value in most of these additions — and for teams moving toward agentic development, the session sync and Chronicle features may matter more than they appear at first glance.



from DevOps.com https://ift.tt/Soxp3Az
Labels:

Comments

Post a Comment

Popular posts from this blog

Mistral Moves Coding Agents to the Cloud — and Gets Out of Your Way

For the past year or so, AI coding agents have been tethered to your local machine. You kick off a task, watch the terminal, and babysit every step. It works — but it’s not exactly hands-free. Mistral just changed that. On April 29, the Paris-based AI company announced remote coding agents for its Vibe platform, powered by a new model called Mistral Medium 3.5. The idea is simple: Instead of running coding sessions on your laptop, they now run in the cloud — asynchronously, in parallel, and without you watching over them. What’s Actually New Coding sessions can now work through long tasks while you’re away. Many can run in parallel, and you no longer become the bottleneck at every step the agent takes. That’s the core pitch. You start a task from the Mistral Vibe CLI or directly from Le Chat — Mistral’s AI assistant — and the agent handles the rest. When it’s done, it opens a pull request on GitHub and notifies you, so you review the result inste...
Post a Comment
Read more

Why the Software Development Tools you Choose Directly Affect Your CI/CD Reliability 

Most conversations about CI/CD reliability start in the wrong place. Teams debug flaky pipelines, investigate intermittent failures, tune alerting thresholds and optimize build times. All of that work is legitimate. However, the decisions that most directly determine whether a CI/CD pipeline is reliable or not were made months or years earlier, during tool selection. By the time teams are debugging pipeline reliability, they are usually dealing with the downstream consequences of upstream decisions that seemed reasonable at the time.   The software development tools a team chooses shape their CI/CD pipeline in ways that are not always visible during evaluation. Understanding those connections is the most practical starting point for teams that want reliable pipelines rather than better pipeline firefighting.   The Integration Surface Problem   Every tool in a software development stack creates an integration surface. Integration surface is the set of connections a tool has with oth...
Post a Comment
Read more

Co-Developing an AI Native Observability Platform  

As AI capabilities continue to evolve, AI is becoming central to managing the growing complexity of distributed, hybrid enterprise environments, enabling more effective analysis, correlation, and automation across interconnected systems.   Traditional infrastructure and specifically network monitoring approaches, often built around siloed tools and static thresholds, struggle to keep pace with the scale, velocity, and interdependencies of modern systems. Further blurring the boundaries between network, application, and infrastructure domains makes it harder to isolate root causes and maintain operational resilience. In this context, AIOps platforms have emerged as one response to the growing need for integrated observability, automation, and data-driven decision-making.   At AI Field Day, Selector AI presented an AIOps platform, which can be considered a foundation for co-creating more adaptive and data-driven network operations. Rather than positioning it purely as a product choice,...
Post a Comment
Read more