oh-my-pi in Visual Studio and VS Code

oh-my-pi is two separate extensions, one for Visual Studio and one for VS Code. The oh-my-pi (OMP) agent runs in an editor 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.

GitHub repository
platforms
Visual Studio 2022 17.14+, 2026, VS Code
protocol
OMP JSONL RPC
license
MIT

Why I built it

oh-my-pi runs in a terminal, and I work in editors. So there are two extensions: one for Visual Studio, which knows the most about a .NET project (the solution, the Error List, the native diff and the debugger), and one for VS Code.

The extensions guess nothing. They start OMP and talk to it over its official protocol instead of scraping terminal output, so what you see in the panel comes straight from the agent.

There is no second configuration either. You set up models, logins, MCP servers and sessions once, in OMP, and the extensions use them.

Two editors, two extensions

Visual Studio

GitHub

An oh-my-pi panel in Visual Studio, docked as a tab next to Solution Explorer. The agent works with the solution, the Error List, the native diff and the debugger.

  • chat with streamed replies, tool steps with their duration and a summary of every turn: time, tokens, cost
  • a Changes section with Visual Studio’s native diff and an Agents section with subagents you can nudge while they work
  • files from the active editor and Solution Explorer, images from the clipboard or dropped in, and long pasted text as its own attachment
  • vs_* tools for the agent: the solution, documents, builds with errors from the Error List, the Output window, projects, the debugger and any Visual Studio command
  • models, thinking levels and the tier router come from OMP; sessions can be resumed, and by default a solution’s last conversation returns when you open it
  • questions and approval requests appear in the chat; nothing is approved automatically
  • one OMP process per Visual Studio instance, started in the solution folder and restarted after a crash

requires Visual Studio 2022 17.14 or later, including 2026 (Community, Professional, Enterprise; x64 and Arm64), and an installed OMP. Installed from a .vsix file.

VS Code

GitHub

An oh-my-pi panel in the Secondary Side Bar on the right, like Claude Code or GitHub Copilot Chat, so the Explorer and your editors stay where they are.

  • Chat, Agents and Changes sections; clicking a file in Changes opens VS Code’s native diff
  • editor context attached to a message with one toggle: the active file, selection, diagnostics and files changed in Git
  • slash commands from OMP (built-ins, skills, extensions) with suggestions as soon as you type /
  • a model picker with favorites and recent picks, showing context window and price, plus auto reasoning effort and fast mode
  • provider rate limits at a glance (Show Usage) without adding anything to the conversation
  • files and folders from the Explorer, images and long pasted text as attachments
  • vscode_* tools for the agent: documents (including unsaved edits), Problems, tasks, the debugger and any VS Code command
  • works locally and in a remote extension host; in Restricted Mode OMP does not start until you trust the workspace

requires VS Code 1.106 or later and an installed OMP. The workspace must be a folder on disk; virtual workspaces are not supported. Installed from a .vsix file.

What is in the panel

Chat
Replies appear as they are 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.
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 the editor’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 several at once from the 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 or folder brings back the last conversation.
Agent questions
When the agent asks for approval or an answer, the question shows up in the chat, and if the panel is hidden you are alerted. Nothing gets clicked for you.

The agent drives the editor

The agent does not just write code in the chat. In Visual Studio it can open a file, fix it in the editor, save it, build the solution and read the Error List, the way you would. In VS Code it works with documents, the Problems panel and tasks, and a task’s result and errors come straight back to it.

It knows the debugger too: it sets a breakpoint, starts the app, steps through and checks variable values. And if something is not covered directly, it runs any editor command, such as formatting or tests.

So you do not 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.

In VS Code, paths in the file tools must also lie inside OMP’s working directory or a workspace folder. The exception is vscode_execute_command: it runs any VS Code command with any arguments, so through it the agent can open, change or run things outside the workspace. Here too, your OMP approval policy has the last word.

The extensions store 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 you need

Visual Studio 2022 (17.14 or later) or 2026, any edition, or VS Code 1.106 or later with a trusted workspace that is a folder on disk (virtual workspaces, such as GitHub Repositories in the browser, are not supported). Plus an installed and configured OMP. The easiest way is to run omp once in a terminal and sign in. You install the extensions from VSIX files.

Each running Visual Studio gets its own OMP, started in the open solution’s folder. VS Code starts it in the first workspace 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 Visual Studio 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.

The VS Code extension needs Node.js 22.12 or newer: npm install, then npm run package writes a VSIX file to install in the editor.

other projects