A while ago I blogged about how we could setup our own multi-agent workflow by using Git worktrees. With Git worktrees you can setup a branch as a separate folder. If you combine this with the GitHub Copilot CLI you could have multiple agents all working simultaneously on multiple branches while you can continue development as well.
Although the process I described works quite well, it remained somewhat cumbersome and was not well integrated into the VSCode development experience. Not anymore with background agents…
The problem with foreground-only agents
By defaullt, the Copilot agent operates in the foreground. When you ask Copilot to refactor a function or write tests, you're essentially blocked until the task completes. Your editor is locked into that conversation, that context, that task.
This works fine for quick queries, but what about:
- Running comprehensive test suites while you continue development
- Refactoring an entire module while you work on a new feature
- Analyzing code quality across your codebase while you fix a bug
- Generating documentation while you implement new functionality
These are tasks that could happen in parallel, but most coding assistants force them to be sequential.
How background agents change this
Background agents flip this model. Instead of blocking your primary workflow, you can delegate tasks that run asynchronously. This isn't just about multitasking—it's about matching the cognitive model of how we actually work. We constantly context-switch between different tasks at different levels of abstraction. Background agents make AI assistance fit that natural workflow.
A background agent can work in its own worktree, running tests, making changes, and committing code—all while you work in your primary workspace. When it's done, you can review its changes and merge them in.
Creating a background agent
There are multiple ways to create a background agent in VS Code. Let me show you one way…
In VSCode go to the Chat window and click on the + sign. Choose New Background agent from the dropdown menu:
You can choose to run the background agent directly in your workspace or give it a separate worktree:
That’s all! You no longer need to create a worktree yourself, but VS Code will handle all the work for you.
You can follow up the active agent sessions (foreground and background) using the sessions view:
Remark: As shown in my post yesterday you can also switch to a background agent during a handoff.
More information
Git worktrees–A first step towards a multi-agent development workflow