Skip to content

v5.3.0 — The One Where It Says Which Universe It Answered From

Choose a tag to compare

@tpierrain tpierrain released this 12 Sep 15:40
· 115 commits to main since this release

What this release is about

Your brain can answer from one part of your life while you believe it is answering from all of it. This release is about saying which one.

If you keep several universes — a past employer and a new one, a few clients, work and personal — your brain narrows its searches to the one you are working in, plus the handful of notes you keep cross-cutting. That is the whole point of them, and it works. What was missing is that it never said so.

A narrowed answer and a complete one look exactly alike. So an answer that covered one universe read as everything you know, a note could be filed under one universe while your searches served another, and switching universe left the conversation you were already in still holding everything it had read from the universe you had just left. None of it was a malfunction: each piece was doing its job, quietly, and quiet is precisely what made the scope impossible to check.

This release makes your brain say, out loud and unprompted, which universe it is working in and what it could not re-scope for you. And since a brain that stays silent about its own scope is the same habit as one that stays silent about a waiting update, the update offer is repaired in the same movement: it now comes back until you answer it, and tells you how long saying yes actually costs.

What you get

When you work in more than one universe (nothing here appears if you have only one)

  • 🧭 It says which universe it answered from. An answer that covered your Acme notes now says it covered your Acme notes — instead of leaving you to remember, days later, which hat it had on.
  • 🔀 Switching now tells you what the switch could not undo. Your next searches are scoped immediately; the conversation already on screen is not, because it still holds what it read before you switched. It says so, and offers you the clean slate if you want it.
  • 🗂️ A note about to be filed in another universe is named before it lands. Not blocked — filing a note elsewhere is a perfectly good thing to do. Just never again without your knowing: fourteen notes once went to one universe while every search served another, and it was noticed by chance.
  • ✍️ A universe name you spell wrong is corrected, not turned into a new universe. Ask for "acme corp" when your universe is acme-corp and it fixes the name, quietly, instead of quietly creating a second one beside it.

When an update is waiting for you (/update-engine)

  • 🔁 The offer comes back until you answer it. It used to arrive once, at the top of a session, in a line that was easy to miss entirely — and on Claude Desktop it did not arrive at all. An update you never heard about is not one you chose against.
  • 🙅 And no thanks really means no. Remind me later means tomorrow, for as long as you like. No thanks backs off three days, then five, then three weeks, then two months, then stops for that version altogether — and a brand-new release starts the conversation again from the top, because refusing one version says nothing about the next. You are asked once a day at most, whatever you do.
  • ⏱️ It says what saying yes costs you: between 10 seconds and under a minute. The only duration you used to read was the scary one, attached to the rare case where your notes have to be re-encoded. An unknown cost is a cost you postpone.
  • 🆕 A brand-new brain knows from its first conversation whether it was born behind. Brains are often installed from a copy of the project that is itself a release or two old.

What you have to do

Ask your brain to update its engine (/update-engine), click Run the update, then restart Claude once. Your notes, your keys, your constitution and the skills you tailored are left alone, as always.


Under the hood

One rule, four surfaces, and that is why they ship together rather than as four fixes. ADR 0044 (narrowing a scope discloses what stayed wide, PROPOSED — the owner's to ratify) is the doctrine: whenever the brain narrows a scope, it says what the narrowing did not reach. #68 is the conversation window left wide; #82 is a scope that is right and never stated; #72 is the filing path moving while the pointer did not; #66 is a fact scoped so hard it does not survive a /clear. Fixed one at a time, those are four mechanisms that end up disagreeing. The nearest precedent in the codebase already said one of the four out loud — the reminder that live connectors do not follow a universe switch — and it is the shape the first three copy.

#68 — the residue a switch leaves behind. runSwitchCli re-points the pointer and retrieval is re-scoped from the next search; nothing said the conversation still held everything read from the universe just left. So the answer looked scoped and was not, which is a trust defect rather than a token one. The new disclosure is appended by the core, beside the connectors one, so the skill only relays it — and it covers both switch paths, not just the fast one (create is a switch too). The /clear suggestion stays advice, in prose, conditional: it is the owner's call, not the machine's.

#82 — the gate the documentation promised and nothing printed. The issue asked to expose "the same marker" the core already prints. That marker did not exist: the switch skill told the agent to look for the literal words below / past the disclosure gate "printed with the offer", and nothing printed them. So the skill sent the agent hunting for a string that was never there, leaving it only the one thing that same paragraph forbids — counting universes. The fix made the documentation true rather than working around it: a gate subcommand now prints exactly those words, reading the registry rather than the pointer (a pointer aimed at an unregistered universe is a damaged brain, not a multiverse). current's output stays one bare slug, pinned twice, because /sync compares it on both sides of a rebase — which is why the gate is a new verb instead of extra output on an existing one.

#72 and #66 — one hook, because they turned out to be the same question asked of the same event. Both watch a note being written: one to say when its universe is not the one you are working in, the other to correct a declared wrong spelling. Two hooks would have been two extra processes in front of every note write, which is a latency budget the owner has already ruled on once. It runs on PreToolUse, and that is load-bearing rather than incidental: the correction rewrites the tool input before the bytes exist, so there is no wrong file to rename afterwards. It is made by the code, never by asking the model to rewrite — a measurement taken before the design was fixed showed why, and it changed the design. The drift notice is said once per session per universe (fourteen identical warnings is noise, and noise is how a net stops being read), while the correction itself is always applied. It never blocks, and auto-switching on a write was rejected outright: guessing intent from one file would move your scope under you.

#100 — an offer that rests on one decision: being asked is itself worth a day. The stamp is written when the offer is spoken, before any answer exists. Everything downstream — the question, your answer, the command that records it — is then an improvement on "ask again tomorrow" rather than a load-bearing part, which is what makes every failure harmless: an unanswered question, a permission dialog you decline, a read-only disk, a conversation abandoned mid-sentence. There is no path through the feature that nags. It rides the hook that already speaks on every prompt, on Desktop as well as the terminal, rather than a new one. While a restart is pending it stays silent, and is not even looked up: you are already being told to close and reopen, and two update instructions at once is how someone does the wrong one first.

#101 — measured, not estimated. The field rehearsal could not answer this one: it stubs npm install and the re-index, so its whole run takes under three seconds. The figure came from a real, un-stubbed update on a copy of a brain installed at v3.4.0 — 9 seconds with no re-index, 24 seconds with one. The sentence states that range rather than a rounded figure, and still leaves room for what the stopwatch could not see: that brain's dependencies were already installed, and a cold install on a slow line is what fills the rest of the minute. A duration you beat is a promise kept. Whether a given update will re-index is not knowable in advance — the answer lives in the launcher's own manifest, which the update reads only after cloning it — so the sentence hedges honestly rather than promising what the machine cannot check.

A fourth door onto an engine script existed, and nothing watched it. A brain runs an engine script through three doors the suite guards: a wired hook, a delivered skill, the constitution. This release opened a fourth — a directive the engine injects into the conversation. The command that records your answer was written, unit-tested, run as a real process by its own suite, and declared in no delivery regime: every test passed, and the feature would have reached you with that command missing, so every no thanks would have gone unrecorded for ever. The new guard asserts on the directive's rendered text rather than on the module's source, and fails if the directives stop rendering, so it cannot go blind in silence. A test that runs a script proves it works, never that a brain will ever have it.

The update path was rehearsed on a copy of a real brain installed at v3.4.0, before the tag: the update landed, 508 engine files were swapped, the retired skill was removed, and the owner's own files came back byte-identical. The rehearsal only ever reads an original — the copy is taken without its history, so a push home is not even expressible.

The marketing surface was re-read whole, and it had gone false in one place: "engine improvements reach you only when you ask for an update". Your brain is now the one who asks, so the guarantee that survives is consent, not who raises it. The daily look-up is still one anonymous request to the engine's public repository, now joined by one at the moment a brain is created.

Closed by this release: #68, #82, #72, #66, #100 and #101.

Reviewed and knowingly left open, because a defect you reported deserves to be told it was seen: #79 is half done — its decision shipped as ADR 0043 in v5.2.0, and the sweep of every existing string is v5.4's whole subject. #78 was considered for this release and deliberately dropped: its engineering half is small, but six items is already a release, and its product half is a question only the owner can answer. #62 is blocked on a design answer rather than on effort: a friction born inside a private vault would travel to a public repository, and nobody can size a de-identification design before it exists.