Unified Agents Blog Post

blogs/2025/11/03/universe-recap.md

@@ -0,0 +1,118 @@
+# A unified experience for all coding agents
+
+Agents took over VS Code in 2025. We released the [GitHub Copilot agent](https://code.visualstudio.com/updates/v1_105#_vs-code-at-github-universe), integration for the [Copilot Coding Agent (cloud)](https://code.visualstudio.com/docs/copilot/copilot-coding-agent), and the new [GitHub Copilot CLI](https://github.com/features/copilot/cli/). But Copilot is just the start - there are now more coding agents than ever, and most don't even have "Copilot" in the name.
+
+With all these choices, things got better - and a little more fragmented. Subscription hopping, tool juggling, and FOMO became the norm. This year at GitHub Universe, we set out to fix that with a unified agent experience in VS Code. Now you can switch between agents - local or cloud - and manage them all from one place.
+
+### OpenAI Codex Integration
+
+[OpenAI Codex](https://openai.com/codex/) was a hit with developers in 2025. Riding the wave of GPT-5 and Codex, OpenAI delivered a top-tier agent experience with the Codex CLI and a solid VS Code extension that brings Codex right into the editor.
+
+This year at GitHub Universe, we announced you can use OpenAI Codex with your GitHub Copilot Pro+ login.
+
+To use this integration, install the OpenAI Codex extension and sign in with your Copilot Pro+ account.
+
+![OpenAI Codex sign-in panel in VS Code](codex-signin.gif)
+
+When you use Codex with Copilot Pro+, Copilot handles all model calls and standard rate limits apply. You get code generation, code explanation, and all the features - no need to manage a separate OpenAI account.
+
+With Codex, you now have four powerful coding agents in VS Code:
+
+1. GitHub Copilot
+2. GitHub Copilot Coding Agent (Cloud)
+3. GitHub Copilot CLI
+4. OpenAI Codex
+
+But with all these agents, it's easy to get overwhelmed. What agents are running? Where are they running? What day is it?
+
+That's why we've introduced a new feature in VS Code for orchestrating all your agents - local or remote. We call it, "Agent Sessions".
+
+### Agent Sessions
+
+There's a new view in the VS Code sidebar called "[Agent Sessions](https://code.visualstudio.com/updates/v1_105#_agent-sessions)". It gives you one place to manage all your agents - local or cloud.
+
+![VS Code window with Agent Sessions sidebar showing Copilot, Coding Agent, CLI, and Codex statuses against a calm gray workspace](agent-sessions.png)
+
+With Agent Sessions, you see all agent sessions for your project. You can check which agents are running, their status, and jump between sessions with a click.
+
+Cloud Agent sessions now have a tabbed experience that lets you course-correct the agent mid-run. It's common to send a prompt and realize you forgot something important. Before, you had to wait or cancel. Now, just open the tab, add an update, and watch the agent adjust its plan.
+
+You can also delegate any task to any agent right from the chat.
+
+![VS Code showing the "Delegate" button from the chat, when clicked opens a menu of agents to delegate to](why-settle.gif)
+
+This unified Agent Sessions view makes VS Code a "mission control" for orchestrating all your agents, while keeping you in the editor where you do your best work.
+
+### Planning Agent
+
+When you use a Chat Mode to alter the agent behaviour in VS Code, what you're _really_ doing is creating your own custom agent. So we've renamed Custom Modes to just "Agents" to better reflect what they actually are.
+
+To get you started with Custom Agents, we've added a new Agent called "[Plan](https://code.visualstudio.com/updates/v1_105#_plan-agent)". You'll find it in the Agent dropdown below "Agent".
+
+![Copilot chat in VS Code with Plan agent dropdown highlighted, planning guidance beside dark theme editor, label reads Plan for a focused tone.](planning-agent.png)
+
+When working on medium to large tasks, having a detailed plan beats an open-ended prompt every time. The less info the model has, the more it guesses. The more it guesses, the more mistakes it makes. Prompt Engineering is the fine art of giving the model the answer that you want.
+
+The new Plan agent helps create a detailed plan from lazy prompts like "add drag and drop". That's an actual prompt I sent yesterday. No mention of what to add it to, what page, or whether to use a library. I do this a lot, and I bet I'm not alone.
+
+With the Plan agent, Copilot asks the questions that need answers. It even recommends libraries for drag and drop and gives reasons to pick one over another.
+
+![Plan agent breaking down drag-and-drop into steps recommending React Beautiful DnD and React DnD with comparisons.](plan-in-action.png)
+
+You can answer these with quick replies on separate lines so it knows which answer goes to which question. Here's how I'd answer:
+
+```
+dnd-kit
+yes - what kind of a question is this in 2025
+link creation only
+```
+
+> Pro tip: Change the "workbench.action.chat.submit" keybinding to "Ctrl + Enter" so you stop accidentally sending messages when you just want a new line. Your swear jar will thank you.
+
+When the Plan agent has enough info, it stops asking questions and asks if you're ready to proceed. You can use the new "[Handoff](https://code.visualstudio.com/updates/v1_105#_handoffs)" feature in chat to either proceed or open the full plan in the editor.
+
+![Screenshot showing the Handoff feature in Copilot chat with options to proceed with implementation or open the plan in the editor.](handoffs.png)
+
+Try different models to see which you like best for planning. We've found the [Claude models](https://www.anthropic.com/claude) are great at identifying missing context and edge cases, and asking the right questions.
+
+If you're like me, you'll want to know how the Plan agent works so you can up your prompt engineering game. You can read the Plan prompt by choosing "Configure Agents" from the Command Palette and selecting Plan. It's a great baseline for creating your own [custom agents](https://code.visualstudio.com/updates/v1_105#_support-for-nested-agentsmd-files-experimental). I used it to create one called ["Research"](https://gist.github.com/burkeholland/919d655ae4df5c809b549632c3afb144) that recursively does internet research and writes up its findings.
+
+> Pro tip: You can find hundreds of custom instructions, prompt files and agents over on the [awesome-copilot](https://github.com/github/awesome-copilot) repo. If you haven't checked that out yet, you're missing out. It's a treasure trove of inspiration and ready-made prompts.
+
+And If you read the Plan prompt, you'll see it make a tool call to something called "[runSubagent](https://code.visualstudio.com/updates/v1_105#_isolated-subagents)".
+
+### Subagents
+
+[Context Confusion](https://www.dbreunig.com/2025/06/26/how-to-fix-your-context.html) is a real problem with agents. The more you interact, the more context they track - and the more likely they are to get confused. There's a whole new discipline for managing context called "Context Engineering".
+
+With the latest VS Code release, we've added a tool called "[runSubagent](https://code.visualstudio.com/updates/v1_105#_isolated-subagents)" to help you manage context.
+
+[Subagents](https://code.visualstudio.com/updates/v1_105#_isolated-subagents) run independently from the main chat and have their own context. You can call one by adding the `#runSubagent` tool to your prompt. The LLM creates a prompt, hands it off to a subagent, and that agent only gets the context you send. It knows nothing about the rest of your chat, and your chat knows nothing about the subagent's context. Subagents don't pause for feedback and have access to most of the same tools as the main chat.
+
+When a subagent finishes, it returns the final result to the main chat - and only that result joins the main context. Subagents keep your main chat lean while letting you go on sidebars and deep dives. For example, if you're building an API and need to research authentication, spin up a subagent to do that.
+
+```
+Analyze the #file:api with #runSubagent and recommend the best authentication strategy for a web client consuming these endpoints.
+```
+
+You'll know a subagent is running because you can see tool calls and model responses below the subagent action. In the screenshot below, that's "Analyze app structure for auth".
+
+![A subagent process running in VS Code with tool calls underneath the main agent action](subagent-in-progress.png)
+
+We're still exploring ways to help you manage context with agents, and subagents are just the beginning.
+
+## Looking Ahead
+
+Agents are changing how we write code and how we work. You shouldn't have to pick just one. You should be able to move between agents, keep fine-grained control over your context, and create your own Agents to extend our system prompts.
+
+These are just a few highlights from this year's [GitHub Universe](https://github.com/events/universe). Check out [GitHub's blog](https://github.blog/) for all the updates as we work on a unified workflow for a multi-agent experience everywhere you need it.
+
+I'll leave you with this: It was only 12 months ago that we announced "Copilot Edits" and Claude support in Copilot. At this pace, imagine where we'll be 12 months from now.
+
+And as always, Happy Coding! 💙
+
+
+
+
+
+