Skip to content

Developer Tools

GitHub Copilot’s July VS Code Agent Updates, Explained

VS Code added worktrees for multiple harnesses, subagent tracking, peer chats, BYOK agent models, vision, and reusable skills.

The Vibe Father 6 min read
Dark code editor and terminal split across a widescreen display
A code editor and terminal arranged for active development. Wikimedia Commons Wikideas1 CC0 1.0
Share Post to X LinkedIn

GitHub’s July 30 roundup covers VS Code 1.127 through 1.131 and makes agent work more visible, isolated, and reviewable. The biggest additions are not another chat button. They are worktree support across Copilot, Claude, and Codex sessions, subagent activity tracking, multi-chat sessions, and faster diff review.

What changed in the Agents window

  • Open files and diffs beside the conversation with a shared tab bar.
  • See additions and deletions per file and switch diff layouts.
  • Start Copilot, Claude, or Codex in isolated Git worktrees.
  • Group and reorder sessions.
  • Inspect a subagent’s model, elapsed time, active tool, and conversation.
  • Respond to failed CI and pull-request review updates from chat.

Multi-chat is more than UI polish

A single Claude agent session can contain related chats with separate histories and models. Developers can fork a conversation into a peer chat without re-explaining the original context. That makes alternate approaches easier to compare, but it also creates more state to govern. Teams need to know which branch produced the accepted patch.

New capabilityGood useGuardrail
Worktree sessionsParallel isolated changesOne owner for integration and tests
Peer chatsCompare two approachesRecord why one was selected
Subagent trackingInspect delegated workDo not treat visibility as validation
BYOK in AgentsProvider choiceApply enterprise data policy

Other useful additions

Copilot vision is generally available for images and PDFs. Business and Enterprise users can see current-cycle AI credit usage. Messages beginning with an exclamation mark can run terminal commands. Prompt files can be migrated into reusable skills. Experimental dictation works across chat, editor, and terminal, with optional transcript cleanup.

A sensible rollout

Enable worktrees first, because isolation reduces collision risk. Define when subagents are allowed, require tests in each worktree, and keep merge authority with a person. Review BYOK data handling before allowing private repositories to reach a new provider.

Bottom line

VS Code’s July releases move agentic coding toward a managed workspace. The practical win is not maximum parallelism. It is being able to see, isolate, compare, and review concurrent agent work without losing the repository’s source of truth.

Source

Reader check

Was this article helpful?

One click helps us decide what to research next.

The app behind this research

TheVibeFather is the multi-CLI AI coding harness

You just read field notes from the same team that ships TheVibeFather — the multi-CLI AI coding harness that runs Claude Code, Codex, OpenCode and more with shared memory and a verify gate. Bring your own keys.

Keep reading