GGovernor

Your details, and a line they don't cross.

Governor holds the facts you would otherwise retype into every new chat — your role, how you like answers, the numbers a calculation needs. Assistants can read it. They can ask to change it. They cannot write to it, and what you mark private never reaches them at all.

Free while it is in beta. Works with Claude, ChatGPT, Cursor and Copilot.

An assistant wants to save three things
Job titleSite Reliability Engineer Shared
Age34 → stored as 30–34 Range only
Gross annual income27,00,000 Private
Save these Discard

Nothing is stored until you press the button. The assistant that proposed this has no way to press it — there is no tool for approving, on purpose.

The problem

You introduce yourself to a machine several times a day.

Every new conversation starts from nothing. So you explain, again, that you are an SRE, that you work in India, that you want the short answer, that your income is the one the tax maths needs.

Assistants have started keeping notes about you to fix this, and that solves the retyping. It creates a different problem: the notes are theirs. You cannot see the whole file, you did not approve what went into it, it lives with one vendor, and moving to another means starting over.

Governor inverts that. The file is yours, on your machine or on an account you control. Every assistant reads the same one. You can see all of it, change any of it, and delete it in one command.

YouWhat's my take-home after tax this year?
Claude reads Governor — new regime, salaried, and the exact income, which never left your machine to get here.
Your take-home is ₹23,17,800. That is on the new regime — with the deductions you actually claim, the old one would leave you worse off.
YouI've moved to the old regime from next year.
Claude Noted. Shall I save that?
proposes one change — tax regime: new → old
YouYes. — approves it in one click

Two things happened there. It answered from what you had already told it once, and it asked before changing anything. The next chat, in any assistant, starts from the corrected version.

How it works

One store. Every assistant. Nothing written without you.

Governor speaks MCP, the protocol Claude, ChatGPT, Cursor and Copilot all use to reach outside tools. You connect it once per app.

1

Connect it

One command for apps on your machine, or one address pasted into ChatGPT or Claude in a browser. Signing in is yours to do, not the assistant's.

2

It reads what it needs

Assistants fetch fields by name rather than hoovering the lot, and every read is written to a log you can look at afterwards.

3

It asks before it writes

Learned something worth keeping? It proposes. You get a page listing exactly what changes, and nothing lands until you say so — which is also the quickest way to fill a vault in the first place. Paste in a CV, or just talk, and approve the batch.

The line

Removing your name is not what makes something private.

Age, city and job title together identify most people uniquely. None of those three is personal information by any ordinary rule, and the combination is close to a fingerprint.

Which is why Governor does not sort facts into "sensitive" and "fine". It grades every field by how much precision the job actually needs, and stores no more than that. Three levels, and you can overrule any of them.

Shared stored as given

Carries no signal on its own

Your field of work, how you like answers, which tax regime you are on. Assistants read these exactly as stored, because knowing them narrows you down to millions of people.

Range only 34 → 30–34

Useful roughly, revealing exactly

Age, years of experience, a city. Governor keeps the band and throws the precise value away at the door — so there is nothing exact for an assistant to read, or for anyone else to find later.

Private kept exact, never sent

Needs to be exact, and needs to stay put

Your income, a weight, a medication. A tax calculation needs the real number, so Governor keeps it exactly — and does not hand it to assistants. Not because you will never want it used, but because it should not travel on its own. You can lend it out for one job, and it locks itself again afterwards.

Refused not from a model

Names you outright

Name, email, employer, a profile link, a PAN. An assistant reading your CV is refused when it tries to save these, and told why. You can still add them yourself — it is your vault — and Governor will say plainly what that costs you.

income 27,00,000 Governor grades it band the assistant reads 20–30L exact stays in the vault for your own maths the line
One field, two destinations. The band crosses to the assistant; the exact figure stays behind and is still there when you need it for a calculation.
Lending something out

Nothing private moves unless you move it.

Marking your income private is not filing it away for good. It says no assistant gets it by default — and leaves the exceptions to you, one at a time, looking at what you are agreeing to.

YouWork out my take-home for this year.
Claude I need your exact income for that, and it is marked private. Here is a link where you can lend it to me for this — it will be locked again afterwards.
governorvault.com/release/rl_4f21…
You opens the link, sees ₹27,00,000 written out, presses Allow
Claude Your take-home is ₹23,17,800.
fifteen minutes later, it is private again — the next chat starts without it
You decide on a page, not in the chat

The assistant can ask. It cannot allow.

There is no tool for approving — the same reason it cannot save anything by itself. Saying yes in the conversation does nothing at all; it only counts on the page.

You see it first ₹27,00,000

The page shows the actual value.

Not the name of a field. You are agreeing to a number you are looking at, along with what the assistant said it wanted it for.

15 minutes then locked again

It lends, it does not unlock.

The window is fifteen minutes, and covers that one assistant. Nothing about the field changes — it is marked private before and after, and the next conversation starts without it.

30 minutes or the link lapses

Ignoring it is a decision too.

An unopened link expires after thirty minutes and grants nothing. Walking away from a request you did not like needs no button, and asking again does not wear you down — each ask is a fresh link you have to open.

Works with

Tested by hand, and reported honestly.

Every one of these connects. They do not all behave identically, and pretending otherwise would waste your afternoon.

AppStateWhat to expect
Claude CodeWorks Finds Governor on its own, unprompted.
Claude DesktopWorks Say the word “governor” in your question, or it answers from its own memory feature instead.
ChatGPTWorks Add it as a custom connector; needs developer mode switched on.
GeminiWorks Same custom-connector flow.
CursorMostly Connects, but often answers by running a command in its own terminal instead of calling the tool. Say “use the governor tool” and it behaves.
GitHub CopilotUntried The configuration is written correctly and nobody has sat down with it yet. Agent mode only — Ask mode ignores MCP servers entirely.
What it doesn't do

Worth knowing before you decide what to put in.

Every tool like this has edges. Knowing where ours are is the difference between using it well and relying on something it was never doing.

It holds context, not secrets.

Governor is for the things you would tell an assistant anyway — your role, how you like answers, the numbers a calculation needs. Marking something private is a real guarantee about assistants: they never receive it. It is not encryption, and on the hosted version nothing is sealed against whoever runs the server. So keep passwords, recovery codes and anything you would call a secret in a tool built for those. If you would rather that question did not arise at all, run it on your own machine instead.

Anything shared reaches the assistant's servers.

That is what sharing means, and no amount of encryption changes it — a model cannot use a value it cannot read. Governor's job is to make sure only what you agreed to gets that far. It will never claim more than that.

It goes by the name of a field, not by understanding it.

Governor grades a field from a set of rules and patterns on its name. income, current_salary and ctc all read as money; city reads as a place and is kept as a wider region. It does not read meaning. Something nobody anticipated is treated as ordinary shareable information — and it says so, on the field, so you can overrule it in a click. What it will not catch is your employer mentioned halfway through a sentence in a free-text note.

One more thing

This page loads nothing from anywhere else.

No web fonts, no analytics, no tag manager, no embeds, no cookies. Opening it makes exactly one request, to one server, for this document.

It would be strange to argue that your details should stay where you put them and then hand your address to three companies on the way in. Check it with your browser's network tab — that is the point of saying it.

The other way

Or keep the whole thing on your own laptop.

Everything above describes the hosted version, where the vault lives on a server I run. There is a second way to use Governor: the vault is a file on your own disk, nothing is on anybody's server, and the question of who else could read it does not arise.

It asks more of you — a terminal, ten minutes, and your own backups — and it has its own trade-offs worth reading before you choose. Both versions are the same program and store the same things, so starting on one and moving to the other is not a decision you are stuck with.

Tell it once.

A vault of your own, in about a minute. Connect an assistant when you are ready.