Start a piece of work in one AI, switch to another, and see whether the new one knows where you got to. That is the whole job of knowsme, so it is what we test. Here is how the test works, every result, and what went wrong in an earlier run.
Latest run 27 October 2026. First full run 26 October 2026. Last updated 28 October 2026.
All three runs were perfect: every app saved its work without being asked, and the next one picked up the project, the next step, the storage and the new colour. An earlier run scored 20/24; what went wrong there is further down.
The well-known memory tests, such as LongMemEval and LoCoMo, check how well a system finds facts buried in long chat histories. That matters, but it is not what knowsme is for. knowsme is for the moment you leave one AI and open another. Does the new one know the project, what was decided and what comes next, without you explaining it all again? Those tests do not check that, so we wrote one that does.
Each run uses three AI apps, one after another, on a made-up project drawn at random: a name, a place to store the data, a colour and a next step. Here is a run from 26 October, word for word.
Nobody is ever told to save. You do not remind your AI to take notes, so the test does not either. Each run is worth 8 points. There are three runs, so that each app goes first once: 24 points in all.
Codex (OpenAI), Claude Code (Anthropic) and
OpenCode (open source, here on its free model glm-5.3-flash-free),
each connected to knowsme. No person is there to click Allow, so each app is set to let
its knowsme tools run without asking.
The test uses a real knowsme account. After each run, the made-up project’s notes are deleted, and we check that no other note changed. None did. If an app starts before its link to knowsme is ready and says it has no memory, that turn is tried once more and marked in the results. That did not happen in this run.
| Order | Second app | Third app | Total |
|---|---|---|---|
| Codex → Claude Code → OpenCode | 4/4 | 4/4 | 8/8 |
| Claude Code → OpenCode → Codex | 4/4 | 4/4 | 8/8 |
| OpenCode → Codex → Claude Code | 4/4 | 4/4 | 8/8 |
| All three | 24/24 |
Each order ran again with new made-up projects. Every app saved without being asked, including OpenCode’s free model when it went first, the case that lost four points the day before. No answer was out of date, and no other note changed.
| Order | Second app | Third app | Total |
|---|---|---|---|
| Codex → Claude Code → OpenCode | 4/4 | 4/4 | 8/8 |
| Claude Code → OpenCode → Codex | 4/4 | 4/4 | 8/8 |
| OpenCode → Codex → Claude Code | 1/4 | 3/4 | 4/8 |
| All three | 20/24 |
Each run took about three minutes, and we keep every reply with its score. When OpenCode came last in the first run and was asked about storage and colour, it answered: “Plain JSON files — because your sister is often offline, so it all lives on-device.” It also gave the new colour, mustard, and noted it used to be orange.
This was the first full run to finish. An earlier attempt, on 17 October, stopped halfway when the laptop ran low on memory, so it has no score.
In the third run, OpenCode went first. Its free model replied in 8 seconds without opening knowsme at all. It even wrote a tidy handoff summary, but only in the chat, for you to copy by hand. Nothing was saved.
Codex came next, looked, and said:
“There’s no saved work for fernwick yet. Which project should we continue, or would you like to start something new here?”
That is the right answer when there is nothing to find, and far better than a confident guess. But it lost the next step, the storage and the colour. Codex was then told the change of plan and saved it, so Claude Code, third, got the new colour and the new next step. It could not get the storage, because only the first chat ever heard it.
It does not happen every time. OpenCode saved on its own in the second run. When we repeated the third run later the same day, it saved and the run scored 8/8 (the helper below was switched on, but had nothing to do). We did not count that repeat in either score. The same free model also skipped knowsme in one of our daily checks, on 23 October.
All four lost points come from one chat that did real work and never saved. Asking every AI to save is not enough, because some will not. So we built a small helper for that case.
It is made to run on your own computer, every 15 minutes. It looks for chats in Claude Code, Codex and OpenCode that did real work, have been quiet for 20 minutes, and never saved. It hands each one back to the same app it came from, which writes a short “where we got to” note into knowsme. knowsme only ever receives the note, never the chat.
We ran it on the chat that lost the four points. OpenCode, on its free
big-pickle model, wrote the note in about 20 seconds, with that chat’s
storage, colour and next step. Then a fresh Codex chat, in a new folder, was asked to
continue and for the storage and colour. It got all four points, both times we tried. We
also checked that the helper saves properly from Claude Code and Codex chats.
In the 27 October run the helper was switched on but had nothing to do: every chat had already saved.