Give the agent in VS Code
your product, not only your files
Add GitMir Vibe to VS Code in one click. VS Code signs you in, the agent connects the repository through GitHub and reads it — and from then on it asks what the product does and what a change reaches before it edits.
KEEP YOUR EXISTING WORKFLOW.
GitMir Vibe Connected directly through GitMir Vibe: one MCP server added to this client. The agent signs in, connects the repository through GitHub and asks the product model from inside the client.
What VS Code already does well
VS Code
- Runs GitHub Copilot's agent in the editor, on the repository you have open
- Reads, edits and runs code across the workspace
- Connects MCP servers per workspace or per user
Keep VS Code and its agent. Give the agent the product it is working on.
One click in VS Code
The same address for every coding tool. VS Code keeps the sign-in; there is no key to copy. To share the server with the team, commit .vscode/mcp.json.
{
"servers": {
"gitmir-vibe": {
"type": "http",
"url": "https://vibe.gitmir.com/mcp"
}
}
}What happens in VS Code after that
- You ask“Connect this repository to GitMir.”
- vibe_statusWhere the repository is — not connected, reading or ready — and the one next step.
- vibe_connectConnects the repository of this folder. Only if GitMir cannot read it yet, it gives you a GitHub link that works for 30 minutes and only for your account.
- vibe_statusReading, after saying what the reading takes. Then ready.
- gitmir_contextBefore a change: what something is, what depends on it and what the change reaches.
- vibe_refreshReads the commits pushed since the model was built, when you ask.
What GitMir adds
- A compact model of what the product does and how it behaves
- The things a change will actually touch, named before anyone opens a file
- The customer paths a change would touch, and how states change along them
- Product-level change across analyzed commits
- Context that survives the session instead of being rebuilt per task
Product understanding for reasoning. VS Code for implementation
VS Code today
- Request
- Agent mode
- Workspace files, search and tools
- Reconstruct the behavior involved
- Implement
VS Code + GitMir Vibe
- Request
- gitmir_context: the product behavior involved
- Reason about the product change
- Exact code
- Implement
See the product layer on a real repository
The public Supabase model is what the agent in VS Code would read before a change: what the change reaches, which areas answer for it, and the files behind every claim.
What must an AI agent know before changing billing?
An example, so you can see the answer without uploading anything of yours.
- Areas it reachesBilling & Subscription · Organization · Usage · Partner Onboarding · Project Settings
- RecordsSubscription · Invoice · PaymentMethod · CustomerProfile · Entitlement · ProjectAddon
- Actions · 33updateOrgSubscription · topUpCredits · redeemCode
- Endpoints · 27PUT /platform/organizations/{slug}/billing/subscription · POST .../billing/credits/top-up
- Screens · 33payment methods · organization billing and usage
- Customer pathsChange an organization's plan
One run, published in full
The one measurement GitMir has published is a 50-question run over a single repository, Supabase. It compared context systems answering the same questions, graded blind against repository evidence.
It did not measure VS Code with GitMir against VS Code without it. That comparison has not been run, and this page claims no result for it.
See what changed in the product — not only what changed in the code
GitMir updates the product representation from analyzed commits and keeps the product-level difference between versions: what the product does, the rules behind it, the things it works with, and the areas they touch.
What changes, and what does not
Is GitMir a replacement for VS Code or its agent?
No. VS Code stays the editor and its agent stays the agent. GitMir changes what the agent knows about the product before it edits.
How does VS Code connect to GitMir?
Through GitMir Vibe, one MCP server at https://vibe.gitmir.com/mcp. Press Add to VS Code above, or add the server to .vscode/mcp.json. VS Code opens GitMir in the browser to sign in — there is no key to copy.
VS Code does not offer to install the server
MCP servers need VS Code 1.102 or later. Update VS Code, then press Add to VS Code again, or add the server by hand: Command Palette → MCP: Add Server → HTTP, with the address above.
The server is added but the agent never calls it
Open Chat in Agent mode — that is where MCP tools run. In the tools list the gitmir-vibe tools must be ticked. Then ask: “Connect this repository to GitMir.”
The server shows as stopped or asks to sign in
Command Palette → MCP: List Servers → gitmir-vibe → Start. VS Code opens GitMir in the browser; sign in once and VS Code keeps the sign-in.
MCP servers are greyed out at work
With a GitHub Copilot Business or Enterprise seat, MCP servers are switched on by the organization's Copilot policy. Ask an organization admin to allow MCP servers in Copilot.
One click. Keep VS Code
Add GitMir Vibe, sign in once and ask the agent to connect the repository. It works from the product model from then on.
10,000 STARTING CREDITS INCLUDED · YOU SEE THE ESTIMATE BEFORE A BUILD STARTS · PROCESSING STOPS WITH YOUR BALANCE AND RESUMES AFTER A TOP-UP