Chat
Replies appear as they're written. Each tool call shows what the agent ran, with what and how long it took, and every turn ends with its time, tokens and cost.
oh-my-pi. Inside Visual Studio.
The oh-my-pi (OMP) agent in a Visual Studio panel, with no jumping to a terminal. You review changes in the native diff, approve the agent's actions in the chat, and it builds and debugs the project itself.
Why did I build it?
oh-my-pi had a VS Code extension and nothing for Visual Studio. Yet Visual Studio is what knows the most about a .NET project: the solution, the Error List, the native diff and the debugger.
The extension guesses nothing. It starts OMP and talks to it over its official protocol instead of scraping terminal output, so what you see in the panel comes straight from the agent.
There's no second configuration either. You set up models, logins, MCP servers and sessions once, in OMP, and the extension uses them.
What's in the panel?
Typing while it works
Enter sends, Shift+Enter adds a line. While the agent works, Enter slips it a hint for the current turn, Alt+Enter saves a message for later and Esc stops everything.
Changes
A list of the files the agent touched. Click one and you get Visual Studio's native diff: before and after.
Agents
Subagents started by OMP get their own section. Expand one to nudge it in the right direction.
Files in the chat
Add the active file or select a few in Solution Explorer. The agent gets the paths and reads them itself.
Models
The model list and thinking levels come from OMP, so a new model shows up without an extension update.
Sessions
New session, history, going back to an old one, renaming. By default, opening a solution brings back the last conversation.
Agent questions
When the agent asks for approval or an answer, the question shows up in the chat and the panel opens itself. Nothing gets clicked for you.
The agent drives Visual Studio.
The agent doesn't just write code in the chat. It can open a file, fix it in the editor, save it, build the solution and read the Error List, the way you would.
It knows the debugger too: it sets a breakpoint, starts the app, steps through and checks variable values. And if something isn't covered directly, it runs any Visual Studio command, such as formatting or tests.
So you don't get a patch to check blindly. The agent compiles it, sees what breaks and fixes it.
Control and security.
Your OMP settings decide what needs your approval. The extension never answers for you, and passwords and other secret answers stay out of the log.
The Visual Studio tools accept only paths inside the open solution or folder. What the agent may do beyond them is decided by your OMP approval policy.
The extension stores no keys or passwords. Remember, though, that code and tool results go to the model provider you chose in OMP. With confidential code, think about that up front.
What do you need?
Visual Studio 2022 (17.14 or later) or 2026, any edition, plus an installed and configured OMP. The easiest way is to run omp once in a terminal and sign in. You install the extension from a VSIX file.
Each running Visual Studio gets its own OMP, started in the open solution's folder. If it crashes, the extension brings it back. What the agent can do depends on your OMP version.
Building from source.
To build the extension yourself you need Windows, Visual Studio 2026 with the extension development workload and the .NET 10 SDK. The repository README walks through it.
F5 opens a separate, experimental copy of Visual Studio, so your everyday install stays untouched. To use a new build day to day, install the freshly built VSIX.