Claude Code forgets everything when you close it. Logbook remembers. It runs on your machine. There is no server of ours to send it to.
sha256 ce87f2af51dc31ee209787c97eb9a59dcc0fcb7b8f1393199b498b3bcb203c66
No. There is no account, no sign-in, no license check, and no server of ours anywhere. We did not build a place to put your work.
Check it yourself. Unzip it and run this inside the folder:
grep -rE "https?://" .
Or read every file in your browser — no download, no account, nobody watching you read it.
It prints every web address in a folder. On ours it prints nothing at all. Then go and run it on everything else you have installed.
Four things, five minutes, no programming. This works on any tool, not just ours.
Open ~/.claude/settings.json and look for hooks. These are the ones
that see the most:
* — a "tool" is anything Claude does
for you: opening a file, running a command, searching. The star means all of them. So a
program gets the result of everything — every file, every command's output,
and any password that scrolled past.It has to reach things to be worth having. Ours does too, or it could not remember anything. This is how add-ons work everywhere — browser extensions, editor plugins, package managers. Claude Code is just where most people meet it, because right now it is the biggest door.
The gap is that nothing tells you who asked for what.
Look for autoUpdate. If it says true, it can replace its own code
without asking. Something that sees everything and rewrites itself: you checked it
the day you installed it, and that is not what is running now.
grep -rE "https?://" .
Documentation links are fine. A server you have never heard of is worth asking about, and "it's only anonymous usage data" is not an answer. If it left your machine, it left your machine.
Open your task manager, or type top. If something you installed is using memory
and processor while you are not using it, find out why.
Memory tools usually run all the time, holding a search database in memory. That can mean gigabytes held and a slice of a processor core, all day — whether you are working or not.
A program that never hands memory back only takes more. Eventually there is none left and the whole computer goes down — at random, mid-work, with nothing obvious to blame.
Logbook does not run. Nothing in the background, nothing in memory. It wakes when you close a session, reads the transcript Claude Code already wrote, and stops.
When the context window fills, compaction has the model re-read the whole conversation to
summarize it — a bill the size of your window, every time. Logbook hands the work to a
fresh context instead, and by default the agent writes that handoff itself:
near the limit it is asked for a baton — where the work stands, in its own
words — and the machine attaches your standing instructions and everything you asked,
word for word. Type /clear and the next context opens with it. If no baton was
written, a local summary (no model call) is carried instead.
logbook baton status # how full the context is, and what is waiting logbook handoff mode seed # machine summary only, if you prefer
logbook stats what it has kept logbook health is it working logbook signal the last thing that broke
It strips tokens, keys and passwords out before writing anything down. To get rid of it all, delete the folder. That is the whole uninstall.
We cannot fix what we do not know about. Logbook does not report its own problems — that would mean phoning home. It shows you a short code instead, and you decide whether to send it. You see exactly what would go, before it goes.
Logbook can import from other tools, and adding one is a small job at our end.
Logbook is the memory. It comes out of Friday Team — a small box of tools that bolt onto Claude Code, each one running on hardware you own. If you are trying to:
that is what Friday Team is for. It is not out yet — it is on the way, and it holds the same line this page does: it runs on your machines and sends nothing to us. When it is ready, it will be here.