GitHub’s October 1, 2026 recap brings together Copilot changes across the September VS Code releases, versions 1.136 through 1.140. The shift is toward coordinating agent work over longer tasks, rather than only requesting a completion in an editor. The official recap is a monthly summary, not a single release date for every feature it contains.
Preview features extend the agent workflow
The recap includes Hydra Fusion research preview, scheduled automations in preview and agent merge in preview. It also describes pull-request creation from multiple agent providers. These developments address the steps between generating a change and getting it ready for a team to review.
Preview status is material. A feature that can propose merge fixes is not evidence that it can decide whether a change is safe to release. Establish who reviews the final diff and which checks run after the last agent edit. Feedback from an earlier commit can become obsolete when a subsequent edit changes the implementation.
Session and environment choices affect collaboration
The VS Code 1.140 notes discuss delegated sessions and development-container behavior. They distinguish the relationship between tasks from the choice of workspace, including whether file changes need isolation. Those details matter when several agents or people work on related code.
A shared checkout is convenient for read-only investigation, but simultaneous edits can make it difficult to attribute a diff. Separate workspaces reduce that collision risk, while creating a new responsibility to combine and verify the results. Choose the arrangement by the work being delegated; a separate session does not automatically mean a separate filesystem.
Adopt the workflow with observable handoffs
For a trial, choose a small repository task with a clear acceptance condition. Preserve the initial commit, examine each agent’s changes and verify the combined result after merge. Include a failed test or conflicting edit so that the evaluation exercises the handoff, not merely a clean demo.
Teams should measure review effort and successful completion alongside generation speed. More orchestration can move work forward, but it can also multiply proposed changes and notifications. The September releases are worth evaluating where task coordination is the bottleneck; enabling every preview at once makes it harder to identify which capability improves the existing process.