Microsoft’s latest Visual Studio Code release expands agent-led development with shared canvases, improved chat continuity and new controls for managing AI permissions across enterprise teams.
Microsoft has shipped Visual Studio Code 1.142 as part of its weekly stable release cycle, continuing the editor’s move towards faster, more frequent updates. According to the official release notes, the latest version broadens the role of AI-assisted development inside the editor, while also refining long-standing workflows for writing, navigation and enterprise oversight.
One of the most visible additions is shared canvases for agent-driven work. Microsoft says these canvases are meant to give developers a more interactive space to coordinate with AI agents outside the normal chat pane. In practice, that pushes Visual Studio Code further towards a mixed environment for coding and task management, with more emphasis on structured collaboration between the developer and the model.
The update also improves continuity in chat-based workflows. Users can now move a chat to another folder or into a new Git worktree without losing the conversation history, which should make it easier to separate tasks while keeping context intact. At the same time, the Markdown editor has been expanded with support for pasting images, renaming file links and using breadcrumb navigation, all of which should reduce friction for documentation-heavy projects. Reports on the release also note that Copilot is now being positioned as the default agent harness, underlining Microsoft’s wider shift towards agent-led tooling.
For larger organisations, Visual Studio Code 1.142 adds more control over how AI agents are used. Microsoft says administrators can enforce sandboxing and permission policies and restrict which permission modes developers are allowed to use. The release also includes a redesigned model picker, intended to make it easier to switch between Copilot and user-supplied models, while adjusting effort levels and context windows in a more direct way. Taken together, the changes show Microsoft trying to balance flexibility for individual developers with tighter governance for enterprise teams.
Disclaimer: This content is intended for informational purposes only. Readers are advised to exercise their own judgement, conduct due diligence, or consult a qualified expert before acting on any information provided.
