GitMir + Codex

Give Codex the product before it changes the code

Add GitMir Vibe to Codex with one command. Codex signs you in, connects the repository through GitHub and reads it — so it can reason about the intended product change before it works through the exact implementation.

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.

Your stack today

What Codex already does well

Codex

  • Inspects repositories and modifies code
  • Runs development tasks end to end
  • Uses external tool and data connections where they are configured

Keep Codex as the coding agent. Give it a reusable product memory.

Connect through GitMir Vibe

One command in Codex

The same address for every coding tool. Codex keeps the sign-in; there is no key to copy and nothing to paste into settings.

Codex
codex mcp add gitmir-vibe --url https://vibe.gitmir.com/mcp

THEN RUN CODEX MCP LOGIN GITMIR-VIBE

Any other MCP client
https://vibe.gitmir.com/mcp

What happens in Codex after that

  1. You ask“Connect this repository to GitMir.”
  2. vibe_statusWhere the repository is — not connected, reading or ready — and the one next step.
  3. 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.
  4. vibe_statusReading, after saying what the reading takes. Then ready.
  5. gitmir_contextBefore a change: what something is, what depends on it and what the change reaches.
  6. vibe_refreshReads the commits pushed since the model was built, when you ask.
The product layer

What GitMir adds

  • A compact model of what the product does and how it behaves
  • The things the product works with, behind the files
  • Requirements, and the development tasks they turn into
  • Product-level change across analyzed commits
  • Context that is reused rather than rebuilt for every task
The workflow

Keep Codex as the coding agent. Give it a reusable product memory

Codex today

  1. Task
  2. Repository exploration
  3. Reconstruct the behavior involved
  4. Implement

Codex + GitMir Vibe

  1. Task
  2. gitmir_context: current product state against the intended one
  3. Codex
  4. Exact implementation
Product proof

There is a public model of Codex itself

This site publishes a GitMir model of the Codex repository, built the same way as every other model here. It is the shortest way to see what the product layer looks like on code you may already have read.

The change on the table

What must an AI agent know before changing billing?

An example, so you can see the answer without uploading anything of yours.

What the product says about it
  • 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
Read from 221 files · 60.7 KB served against 0.76 MB of sourceOpen it and ask your own →
What has been measured

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.

8%of the answer score lost to errors and omissions, against 22% for the best-scoring alternative in that run
8.4Ktokens of context per question, against 27.4K
$0.07per question, against $0.19
Not measured

It did not measure Codex with GitMir against Codex without it. That comparison has not been run, and this page claims no result for it.

Product change history

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.

Questions

What changes, and what does not

Is GitMir a replacement for Codex?

No. Codex stays the coding agent. GitMir changes what it knows before it starts.

How does Codex connect to GitMir?

Through GitMir Vibe. Run the command above, then codex mcp login gitmir-vibe — Codex signs you in through the browser, and there is no key to copy.

One command. Keep Codex

Add GitMir Vibe, log in once and ask Codex to connect the repository. It starts 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