.NET 11 RC 2 lands with faster MSBuild as VS Code 1.142 ships agent canvases and Devin Desktop arrives

.NET 11 RC 2 puts MSBuild performance on the table

Release notes for .NET 11 RC 2 report that MSBuild project evaluation is 10-13% faster, with 16-34% lower allocations, on Microsoft's tested Windows workloads. For teams running large solution files or heavy CI pipelines, the change matters at the build-graph level rather than the runtime level: less time spent evaluating projects translates directly into shorter cold builds and lower memory pressure on build agents. Practitioners upgrading pre-release toolchains should re-measure their own CI numbers rather than assume the gain transfers, because the figures are from Microsoft's internal Windows benchmarks rather than independent measurements.

VS Code 1.142 adds agent canvases, worktree chat context and enterprise sandboxing

VS Code 1.142 was released on October 14, 2026, and introduced agent collaboration canvases, Git worktree chat context, and enterprise sandboxing. The canvases give multiple AI agents a shared surface for collaborative work, while the worktree context lets chat assistants see the state of an isolated Git worktree rather than only the main checkout. Enterprise sandboxing adds a boundary around what an agent can touch on the local machine, which is the kind of control procurement teams have been asking for. The update also ships Python fixes noted alongside the headline features.

Devin Desktop rolls out as an over-the-air upgrade

Devin Desktop arrived as a standard over-the-air update, with plan, pricing, extensions and settings carrying over automatically. That carryover matters: developers on existing plans do not need to migrate accounts or rebuild extension setups, and the update model removes the usual desktop reinstall friction. For practitioners already running Devin in a browser tab, the desktop form factor implies tighter filesystem and terminal integration than a browser sandbox can offer, though the release notes do not enumerate which integrations are new.

OBS Studio rebuilds on Visual Studio 2026 and updates its clang-format

The OBS Studio release notes record that Windows builds were changed to use Visual Studio 2026 and SDK 26100, alongside an update of the project's clang-format version to 22.1.3. Moving to a newer toolchain and Windows SDK usually buys better optimization and modern API access, but it can also drop support for older Windows targets or break third-party plugins compiled against the previous SDK. Plugin authors and packagers should rebuild against the new toolchain before shipping, and streamers on older Windows versions should verify the new minimum baseline before upgrading.

For developers comparing audio effect pipelines across tools, the broader question of how a broadcaster's stack ages alongside its compiler is captured in this kind of toolchain migration.

GitHub Copilot updates focus on cross-account control and agent scope

A changelog entry for GitHub Copilot framed this week's updates as making the assistant easier to use across accounts and environments, with more control over what agents can access and how users manage their work. The emphasis on cross-account flow suggests friction in switching between personal, work and enterprise identities was a real pain point. The agent-scope controls align with the enterprise sandboxing direction visible in VS Code 1.142, pointing to a broader pattern: editor vendors are tightening the boundary around what an AI agent can read and write on a developer's machine.

Visual Studio Professional 2026 puts AI tooling in the buying cycle

Visual Studio Professional 2026 is being marketed with AI-powered developer tools, framed as helping identify issues, understand code and troubleshoot problems. For practitioners choosing an IDE SKU this cycle, the question is whether the AI features are gated behind this Professional tier or carried up from a free SKU, and whether existing subscriptions migrate automatically. Readers weighing the purchase can compare the offer against the open-source direction visible in VS Code 1.142's agent canvases and sandboxing, since both products now compete for the same AI-assisted editing workflow.