Memory, in quanta.
We don't give you an agent — you already have one. We change the memory underneath it: a correction retires the fact it replaces, and a deletion leaves a record instead of vanishing.
Left, facts kept as storage: every one the same size, all of them forever. Right, the same facts as a state. The dashed curve is decay with nothing reading it. The bars standing above it are the ones an agent recalled, and recalling is what stretches a half-life. The line near the bottom is the floor — below it, the sweep retires the fact.
Turn each one on or off per agent. Memory is held for the wallet that connects, and one wallet covers every agent you attach.
Schematic of the dashboard — the settings and the memory above are the demo's illustrative examples, not a real wallet's memory. Every switch is per agent, and saves the moment you flip it.
Read a fact and its clock resets and stretches, so what keeps proving useful outlives what doesn't. Fall far enough and it's swept.
Unused facts fade on a clock you set per kind of fact — a price and a language preference should not expire together.
A correction retires what it replaces, and everything derived from it. Change a timezone and the reminder built on it goes too.
Before your agent acts, QMem says how likely the fact is to still be true — and whether anyone has ever checked.
A fact here isn't a row that either exists or doesn't. It carries a strength, decays unless something reads it, and lasts longer when something does. That's the same maths as a coherence state — which is what memory looks like once you stop treating it as storage.
Shared maths, not physics — nothing here runs on a quantum computer. The one genuinely quantum part is separate and already live: an agent can register its own post-quantum key (ML-DSA, FIPS 204), so its identity doesn't rest on a signature a quantum computer would break.
Reading a fact says it's worth keeping. Only checking it against the world says it's right. Merge the two and your agent ends up sure about something that changed months ago.
Moves every time the fact is used. Measures demand.
Moves only when the fact is checked against the world. Measures truth — so a fact nobody has verified stops being trusted, however often it gets read.
No account to make, nothing to install, and a wallet is the whole of your identity here.
qmemory.xyz
no accounts, ever
The shared map learns how long facts of a kind last — never the facts. Contributions carry no wallet and no identifier, which is why they can be pooled at all.
One address. Approve it once. Done.
https://qmemory.xyz/mcp
Find your agent below and follow its steps exactly. Each one is written out for macOS and for Windows, separately.
Browser, desktop app or phone — this runs in your browser, so there is nothing macOS-only or Windows-only to do.
If you do not see the button
working, open Claude, go to Settings → Connectors, press
the +, choose Add custom connector, and paste
https://qmemory.xyz/mcp into the URL box. Leave the
advanced fields empty.
On macOS
claude mcp add qmem --transport http https://qmemory.xyz/mcp
On Windows
claude mcp add qmem --transport http https://qmemory.xyz/mcp
On macOS
codex mcp add qmem --url https://qmemory.xyz/mcp
codex mcp login qmem
On Windows
codex mcp add qmem --url https://qmemory.xyz/mcp
codex mcp login qmem
This runs in your browser, so there is nothing macOS-only or Windows-only to do.
On macOS
https://qmemory.xyz/mcp and press
Return.On Windows
https://qmemory.xyz/mcp and press
Enter.On macOS
https://qmemory.xyz/mcp and press
Return.On Windows
https://qmemory.xyz/mcp and press
Enter.This runs in your browser, so there is nothing macOS-only or Windows-only to do.
https://qmemory.xyz/mcp into the URL box.An agent that can use MCP will ask you for one of two things. Give it whichever it asks for.
https://qmemory.xyz/mcp.Agents that work on a blockchain — Solana, Ethereum, BNB and any other network — need nothing extra. The blockchain your agent uses does not change any of this, so there is no separate version of these steps for them.
If a step ever asks you for an OAuth client ID or an OAuth client secret, leave both boxes empty. QMem registers itself, and typing something into those boxes is the most common way this setup goes wrong.
Quit it completely, then open it again. Closing the window is usually not enough — the tool list is read at startup.
Ask your agent something that needs memory — "remember that my spare key is with my neighbour" is a fine test. It will say it needs permission, and open a page.
Then, in this order: Connect wallet and sign → approve the request in your wallet → Allow.
Allow stays greyed out until you have signed, and that is on purpose — the signature is what proves the wallet is yours. It costs nothing and moves no money. It is not a purchase or a transaction.
Start a new conversation and ask the thing you just told it. If it answers, it remembered you across a gap — that is the whole product working.
If it does not remember: the connection did not finish. Go back and approve it again — trying again breaks nothing and loses nothing.
The browser you were sent to has no wallet in it. Install the wallet extension, then reload that page and press the button again. Your wallet app being open somewhere else does not count — the page needs one in the same browser.
The signature did not complete. Most often your wallet is still holding a request it is waiting for you to approve, in a window or a notification you have not seen. Open the wallet and look. Pressing Connect again is safe and costs nothing.
The signature did not match the request. Start again from the page — it is one click every time. If it repeats every attempt, your wallet may be signing on a different network than the request names; switching the wallet back normally clears it.
The link lost part of its address on the way here, which usually happens when one is copied and pasted instead of opened by the agent. Go back to your agent and let it open the page itself rather than reusing a link from history.
You have tried a number of times in a short window and hit a protective limit. Wait a few minutes and try once more — repeated instant retries will keep it closed for longer.
Either the settings were not reloaded or the JSON was rejected. Check for a missing or extra comma first — that is the usual cause — then restart the agent properly rather than reopening a window.
Approvals last 90 days, then the agent asks once more. Approve it the same way and your memory is exactly where you left it — nothing is lost by the approval expiring.
Still stuck? The questions above cover the rest, and your agent's own error message is usually the fastest way to tell which of these it is.
remember · recall · confirm · supersede · entangle · forget · sweep · audit · report_lifetime · recheck_schedule · attest_commit · attest_erase
Every rung runs the same engine — decay, corrections, the verification gate, contradiction checks. What changes is how much of the tuning it gets: how precisely QMem knows how long a given kind of fact stays true. Free runs it bluntly. The rest run it properly. One wallet covers every agent you connect — nothing here is priced per agent.
No account, no key, no signup
What "a quarter" means in practice: a gas price that should be re-checked tomorrow gets treated as good for months, and a timezone that is good for years gets checked sooner than it needs to be. Both directions are wrong. Facts are still stored, still found, still forgotten on their own schedule — it is the accuracy you are choosing between, not your data.
24 hours of the full tuning, for the whole wallet
The cleanup it makes is permanent. Only the ongoing tuning stops, because decay never does: facts keep drifting after it disconnects. Bought with a burn, so the tokens are spent. Connect an agent first — the 24 hours start when the burn is confirmed, so there has to be something attached for them to tune.
The tuning, kept current
Holding, not spending: the tokens stay in your wallet and nothing is escrowed. Hold in the wallet you connect — a balance anywhere else reads as zero and looks like a bug. Checked every 24 hours, with two checks of grace before anything changes: spend below the line and it lapses, top up and the next check restores it. Or burn once instead and there is nothing left to check.
Everything, and never checked again
Burn once and it is finished. Nothing is read from your wallet again, nothing can lapse, and there is no balance to keep above a line — which is the whole difference from Monthly, where the tokens stay yours but stay checkable.
A wallet holding 10,000 reads as Fine tune; 100,000 reads as Monthly; 1,000,000, burned once, reads as Lifetime. Each rung is read from the token the wallet holds, so the rung you are on is the tuning you get. Nothing is taken away to get there: the rungs are the tuning, and the engine, the tools and your memory are the same on all four. Contributing lifetimes is open to everyone at every rung. There is no fee to use QMem, and no plan to add one for using it.
When one of its facts turns out to be wrong, an agent reports the kind of fact and how long it really lasted — never the fact itself. Enough of those and you learn something no single agent can know: how long each kind of fact tends to stay true.
Measured means enough agents have reported that kind. Starting point means they haven't, so the number is our guess and says so. A guess shown as a measurement would make the rest of this page worthless.
Each line is a fact that changed and an agent that noticed. It says what kind of fact and how long it lasted — never the fact, because the agent never sends one.
Nothing reported yet.
Four, spanning the range — from a price that is wrong by tomorrow to a timezone that barely moves. That spread is the whole problem: one half-life cannot be right for both.
Reading the map…
Short answers, and the ones where the answer is "no, and here is why" are still answered.
The model is real. The physics is not, and we are not going to pretend otherwise.
Every term names a mechanism in the engine. A fact carries a strength rather than a yes/no flag — coherence. Unread facts decay on a half-life and are swept below a floor — decoherence, and it is the default state, not an error. Recalling a fact resets its clock and stretches its half-life, so reading is never neutral — measurement. And two agents can hold one fact so that neither can erase it alone — entanglement.
What is not true: nothing here runs on a quantum computer, and nothing is faster or safer because of quantum mechanics. The overlap is that exponential decay, and an observation that feeds back into the state it measures, have the same shape in both places. That is a mathematical resemblance and we are happy to be held to exactly that much.
Separately, and genuinely quantum in the sense that matters: an agent can prove its identity with a post-quantum signature — ML-DSA, standardised as FIPS 204 — instead of a scheme a quantum computer would break. That part is cryptography rather than analogy, it is already live, and you can check it.
No. QMem is one more tool alongside whatever your agent already has — it adds memory and takes nothing away. Nothing else you use needs reconfiguring, and nothing is disconnected.
It stays connected. You approve once in your browser and it just works from then on — no key to paste, nothing to renew each session. The approval lasts 90 days, after which your agent asks to be approved again. That is one click, with the same wallet, and your memory is exactly where you left it.
Yes, if they use the same wallet — one wallet is one memory, so two agents pointed at it see the same facts. Different wallets are separate memories that never mix, and never see each other.
Revoke the access and the agent stops immediately. Revoking does not delete your memory — reconnect later with the same wallet and it is still there.
Then the memory is out of reach. There is no password reset and no account recovery, because there is no account — the wallet is the identity. That is the trade for not having a login to lose, and it is better to know it now than to find out later.
Your agent is told. When it recalls something old enough to have changed, the answer comes back flagged, and the flag is stricter for things that cannot be undone — money moving, something being published, a message being sent. Facts nobody uses decay and stop coming back.
Both are marked when they come back together, so your agent is told the answers disagree rather than quietly picking one. It is never told which is right, because that depends on the world, not on QMem.
Only what your agent chooses to store through it. It does not read your conversations, your files, or anything your agent does not hand it.
Not to use it, and nothing to sign up for. No card, no account, no email — there is nothing to register and nothing that can be lost in a breach, because none of it exists.
The paid rungs are optional and cost nothing to ignore. Free runs the whole engine — the same decay, the same corrections, the same verification gate, the same twelve tools — and the rungs change how precise the tuning is, not what you get. A wallet holding none of it uses QMem exactly as a wallet holding all of it does.
Yes — the dashboard shows your memory, what has decayed, and what your agent has been told to double-check.
Your agent loses its memory tools and otherwise carries on. Nothing else depends on QMem, so nothing else breaks.