GitHub's VS Code July Update Adds an Agents Window for Claude, Codex, and Copilot
The Agent Host brings local, background, and cloud sessions into one view while adding multi-chat, subagent visibility, and worktree isolation for multiple coding harnesses
Key takeaways
GitHub summarized the July 2026 Copilot releases for Visual Studio Code on July 30, 2026. The public-preview Agents window brings local, background, and cloud sessions into one view, while the Agent Host can run coding harnesses such as Claude Code, OpenAI Codex CLI, and GitHub Copilot CLI. VS Code 1.131 also adds multi-chat support and worktree isolation for any harness, with clearer session status and subagent structure. For users, the practical opportunity is parallel task management without mixing branches or context. Adoption checks should cover permissions, repository scope, worktree cleanup, cost limits, logs, tests, and human review before real code is merged.
# GitHub's VS Code July Update Adds an Agents Window for Claude, Codex, and Copilot
Published or updated: July 31, 2026
Table of contents
- Direct answer
- Fact sources
- Action steps
- Why it matters
- Impact for ordinary AI users
- Related tools and tutorials
- FAQ
- Source links
Direct answer
The update is not simply another chat panel. It turns multiple AI coding sessions into a visible task queue. The Agents window centralizes local, background, and cloud sessions; the Agent Host can run Claude Code, OpenAI Codex CLI, GitHub Copilot CLI, and other harnesses; multi-chat and worktree isolation reduce context and code collisions between tasks.
Fact sources
GitHub published its Visual Studio Code July 2026 Copilot roundup on July 30, covering the public-preview Agents window, the Agent Host, multi-chat, subagent trees, session status, worktree isolation, and model management. The post treats stable releases 1.129, 1.130, and 1.131 as one coordinated improvement to the agent experience.
VS Code 1.131 says the Agents window manages local, background, and cloud sessions from one centralized view. The Agent Host supports multiple coding harnesses, including Claude Code, OpenAI Codex CLI, and GitHub Copilot CLI. The same release allows multiple chats in one workspace and can isolate changes in a worktree for any harness.
VS Code 1.130 added cross-window session discovery, subagent hierarchy, and persistent background-session status. VS Code 1.129 introduced the first Agents window for viewing in-progress, completed, and archived sessions by state and source. Together, the releases address discovery, switching, isolation, and review for parallel agent tasks rather than a single-response benchmark.
How to test multi-session AI coding in VS Code
- Enable the Agents window in a sample repository and first observe session sources, status, switching, and archiving without production credentials or customer code.
- Record authentication, model choice, billing owner, repository permissions, and callable tools separately for Claude Code, Codex CLI, and Copilot CLI.
- Give each parallel task an isolated branch or worktree plus an explicit objective, allowed directories, test command, and prohibited actions.
- Verify that subagent trees, background status, terminal commands, file changes, and network calls are traceable. Do not merge steps that cannot be explained.
- Limit concurrent sessions, task duration, and model budget so parallel work does not multiply cost and review load without control.
- Merge only after tests pass, diffs are readable, conflicts are resolved, and a human reviewer approves the result.
Why it matters
AI coding tools are moving from one chat toward multi-session task management. Parallel work can increase speed, but it also multiplies branch conflicts, mixed permissions, uncontrolled spending, and missed review. The value of the Agents window, Agent Host, and worktree isolation is better visibility into task state, runtime entry points, and code boundaries. They do not replace testing, code review, or least privilege.
Impact for ordinary AI users
For ordinary users applying AI to code, scripts, document workflows, or automation configuration, the new management layer can split large work into smaller comparable tasks and switch between harnesses. Users still need to know what each session read, changed, authorized, spent, completed, and how it can be rolled back.
Related tools and tutorials
Existing ENHE pages explain Git worktree isolation and compare desktop, CLI, and editor-based AI coding tools. The software, skill-learning, and account-service sections can then be used to verify tool entry points, testing methods, permission scope, and cost ownership.
Git worktree isolation guide; AI coding desktop tool comparison; AI software and tool entry points; AI coding skills and safer testing tutorials; AI account permissions and cost services.
FAQ
Does the Agents window manage only GitHub Copilot?
No. VS Code 1.131 describes a multi-harness entry point that can show sessions from Claude Code, OpenAI Codex CLI, GitHub Copilot CLI, and other supported agents. Availability still depends on versions, extensions, accounts, and organization policy.
What is the difference between multi-chat and a worktree?
Multi-chat separates conversational context. A worktree separates the working directory and branch state. Parallel coding tasks often need both forms of isolation.
Should several agents edit the main branch at the same time?
No. Use isolated branches or worktrees, constrain directories and commands, run tests, and require human review before merging.
Source links
- GitHub Changelog：GitHub Copilot in Visual Studio Code July 2026 releases（2026-07-30）
- Visual Studio Code 1.131 Release Notes（2026-07）
- Visual Studio Code 1.130 Release Notes（2026-06）
- Visual Studio Code 1.129 Release Notes（2026-05）
- Visual Studio Code Docs：Agent Host
- Git Documentation：git-worktree
What this means for everyday users
ENHE users can treat the Agents window as a task board, but each harness still needs separate checks for identity, permissions, model cost, repository scope, logs, and merge ownership.
Related reading
GitHub Copilot Fusion Is GA: How to Choose Standard, High, or Max
GitHub made Copilot Fusion generally available on October 28, 2026. Instead of choosing a model for each step, users select Standard, High, or Max effort while Fusion routes and orchestrates models through single-model, cascade, or critique workflows. Administrators control which models Fusion may use and whether it is the default. The feature is available across all Copilot plans in VS Code, the Copilot app, Copilot CLI, and JetBrains IDEs. Each model used is billed at its standard rate; paid plans receive a temporary 30% discount on model costs. This guide shows how to compare the three effort levels with one task, fixed acceptance criteria, elapsed time, and complete usage evidence.
GitHub Copilot Can Generate and Edit Images: Check Cost, Watermarks, and File Output First
GitHub introduced a public preview for generating and editing images in Copilot on October 28, 2026. A user can describe an asset in VS Code, the GitHub Copilot app, or Copilot CLI. The selected reasoning model calls a dedicated tool powered by GPT Image 2.5 Flare, previews the result inline, and saves it into the project. The preview is available to Pro, Pro+, Business, and Enterprise plans. Image tokens are billed separately from the chat model against AI credits, and the visible “Made with AI” watermark is optional and off by default. This guide provides a bounded asset test covering input, output location, review, disclosure, and cost evidence.
GitHub Copilot SDK Adds Server-to-Server Authentication: Validate Identity, Billing, and Budgets
GitHub launched a public preview of server-to-server authentication for the Copilot SDK on October 27, 2026. A GitHub App installed on an organization can use a short-lived installation access token to make Copilot requests without relying on one signed-in user. Usage is attributed and billed to the organization that owns the installation, and the organization’s model policies, budgets, and spending controls apply. This article helps development, platform, and security teams evaluate the preview without treating workload identity as unlimited authority. A minimal acceptance plan covers the read-only Copilot request permission, token lifetime and storage, organization attribution, model policy, spending limits, audit evidence, revocation, and fallback.
GitHub Copilot Assisted Permissions Is GA: Which Requests Still Need Human Approval?
GitHub made assisted permissions generally available on October 26, 2026 across Copilot CLI, the GitHub Copilot app, and Visual Studio Code. When Copilot asks to run a command, access a file-system path, or open a URL, a language model evaluates the request. Requests classified as clearly safe can proceed automatically, while other requests still require user approval. Administrators can choose a default permission mode for new sessions, and a session falls back to manual approval when the default is unavailable or prohibited by policy. This article gives users and administrators a practical acceptance test with one harmless request, one sensitive request, policy fallback, logs, and a stop condition.
GitHub Copilot Metrics Add OpenCode and Other Clients: Requests Are Not Prompts
GitHub added totals_by_client to the Copilot usage metrics API on October 23, 2026. Enterprise and organization reports can now show model traffic from OpenCode, Claude Code, Codex, Zed, Copilot CLI, GitHub apps, cloud agents, code review, VS Code, JetBrains, and other clients. This article helps administrators build reliable one-day and 28-day reports without confusing model calls with user prompts. It explains request, session, token, model, and selection-mode fields; separates client traffic from agent-app jobs; and adds checks for unknown identifiers, empty arrays, permissions, and coverage. The result is a governance trend report, not an exact invoice or individual productivity score.
GitHub Copilot in Teams Turns Notifications Into Pull Requests: What to Check Before Review
GitHub updated its Microsoft Teams app on October 23, 2026, so an issue notification in a channel, group chat, or private chat can become a Copilot task that investigates the problem, proposes a fix, and opens a pull request. This article helps development and product teams adopt the workflow without mistaking an automated pull request for shipped code. It explains the consolidated app, repository connection, the November 16 retirement of the legacy GitHub app, and the review boundary. A practical acceptance checklist asks teams to reproduce the issue, inspect changed files, run targeted tests, verify permissions, and keep merge and deployment as explicit human decisions.
Summary
The VS Code July update moves AI coding from chat toward session orchestration. Success is not the number of agents running at once, but whether every task has an isolated boundary, visible state, constrained permissions, reproducible tests, and a human merge decision.