Visual Studio Code 1.142 was published on October 14, 2026, with preview canvases for agent workflows, portable chat sessions, Markdown editing changes, enterprise permission controls, and a Windows terminal-sandbox migration. Microsoft also says the Copilot harness is progressively becoming the default for new agent sessions.

For CTOs and engineering leaders, the signal is clear: agent-first development is moving beyond chat into workspace orchestration, policy enforcement, and isolated execution. Your team now needs to evaluate workflow benefits and governance requirements together.

1. Interactive Canvases Extend Agent Workflows

What it is

The 1.142 release announcement introduces Interactive Canvases in preview. Microsoft says users can create canvases or install canvas extensions, including options designed for Kanban planning and implementation tracking.

This is not another static editor pane. It is an extensible surface for organizing work around an agent session.

Why it matters

Interactive Canvases could bring planning artifacts and implementation activity into the same development environment. For platform teams, that creates an opportunity to test whether agent-driven planning can reduce context switching without weakening existing review practices.

Preview status is the governing constraint. Your team should evaluate canvas extensions in a controlled environment, document what project information they expose, and avoid treating preview workflows as an approved production dependency.

2. Agent Chats Can Move Between Workspaces

What it is

According to the 1.142 release announcement, users can move agent chats to another folder or Git worktree while preserving conversation context. A developer can therefore shift the working location without discarding the active discussion.

The capability aligns agent sessions with repository workflows that separate tasks across folders or worktrees.

Why it matters

Preserved context can reduce the repetition required when implementation moves into an isolated worktree. That matters when a conversation already contains requirements, attempted approaches, or decisions relevant to the task.

Your team should still verify that the destination workspace matches the assumptions established earlier in the conversation. Preserved context is useful, but stale path, branch, or repository assumptions can produce incorrect actions after a move.

Why this matters: portability changes an agent chat from a workspace-bound interaction into a reusable development artifact. Teams need conventions for when to continue a session and when changed context warrants starting over.

3. Markdown Editing Gains Structural Improvements

What it is

Microsoft’s release announcement lists direct image pasting, file-link renaming, heading navigation through Outline and breadcrumbs, and safer copying of code blocks among the Markdown editor changes in 1.142.

The editor also displays each Markdown source line separately while editing. According to the release coverage, read-only mode continues to present normally rendered Markdown.

Why it matters

These changes reduce friction for teams that keep documentation beside source code. Direct image pasting can simplify asset insertion, while file-link renaming can reduce the manual correction required when documentation files move.

Separate source-line rendering also makes document structure more visible during editing. Meanwhile, Outline and breadcrumb navigation give authors another way to move through longer technical documents by heading.

For engineering leaders, the implication is operational rather than cosmetic: documentation workflows can remain inside the editor for more of the authoring cycle. Your team should validate image locations, renamed links, and copied code blocks through its existing documentation review process.

4. Enterprise Policies Restrict Agent Permissions

What it is

The Visual Studio Code release announcement says enterprise administrators can enforce sandboxing policies and restrict the permission modes available to agent sessions. The documented example permits Assisted Approval while blocking Allow All.

This introduces an administrative boundary between installing agent capabilities and granting unrestricted agent permissions.

Why it matters

For regulated industries, permission governance is non-negotiable. An agent feature that works for an individual developer may still be unsuitable for organizational deployment if administrators cannot constrain its execution model.

The new controls give enterprise teams a basis for matching agent permissions to internal risk requirements. A policy can retain assisted operation without making the least restrictive mode available.

What this means for enterprise teams: deployment planning should now include an explicit permission-mode decision. Administrators should define approved modes, test the resulting developer experience, and document the escalation path for workflows that cannot operate within those restrictions.

5. Windows Sandboxing Moves to Agent Host

What it is

Microsoft says Windows sandboxing for terminal commands in Local agent sessions is deprecated and unsupported in 1.142. Sandboxed command execution on Windows must use an Agent Host session instead.

Separately, Microsoft says the GitHub Copilot harness is being progressively introduced as the default for new agent sessions. A progressive rollout means teams should not assume every environment has switched at the same time.

Why it matters

The Windows sandbox change requires action now. This is not a future preference between equivalent session types—Microsoft describes the Local-agent option as unsupported.

Teams that rely on sandboxed terminal execution should identify affected Windows workflows and validate them through Agent Host before wider editor deployment. Testing should cover the commands agents invoke, the approvals developers see, and the enterprise permission policies applied to those sessions.

The Copilot harness rollout adds a second variable. Because Microsoft describes it as progressive, support teams should record the session environment when investigating differences between users rather than assuming identical behavior across the organization.

The Bottom Line

Visual Studio Code 1.142 advances agent workflows while making their execution boundaries more explicit. The opportunity is broader orchestration; the immediate obligation is controlled migration and policy validation.

  1. Pilot canvases separately. Treat Interactive Canvases and canvas extensions as preview capabilities, not established production dependencies.
  2. Define chat-mobility conventions. Decide when context should follow work into another folder or worktree and when a clean session is safer.
  3. Set approved permission modes. Use enterprise controls to align agent operation with organizational risk requirements.
  4. Migrate Windows sandboxing. Validate affected Local agent workflows through Agent Host because the previous sandbox path is unsupported.
  5. Track harness differences. Record session details during support investigations while the Copilot harness rollout remains progressive.

Getting the Update

Teams evaluating 1.142 should consult the official Visual Studio Code update page for the complete release notes before deployment. The rollout plan should prioritize Windows sandbox validation, enterprise permission configuration, and a bounded preview of Interactive Canvases.

Happy Coding!