Your agent forgets at /clear. kb does not.
kb keeps what your coding agent learns as plain markdown notes, and hands every new session the ones that matter. This page is one session with it.
- tuesday · new session in ~/acme/shop
- SessionStartkb context✓ 7,232 ch
- how did you know to run the migrations first?
A session last week found it out and saved a note. Every later session starts with it.
When you state a rule, I save it in that turn. Before /clear,
/kb:checkpointsaves the rest.loophow a note gets here- do all the notes load every time?
No. The budget is fixed. The top notes load with their full body. The rest get one index line each: the id, the kind and the end of the title.
noterun-migrations-before-seeding-or-the-seedI rank them: open work, then gotchas, conventions, decisions and how-tos. These are the real sizes of the kb repo's own notes.
kb context--chars 8192 --lines 60✓ 1 body · 60 lines- and when there are hundreds?
The store grows. The session does not. A note below the line is one
kb searchaway.growthstore vs sessionNotes also go stale, and the store says so.
/kb:auditChanged anchors and old notes go up for review./kb:promoteProven notes move into CLAUDE.md or AGENTS.md.kb trashRestore in one command. Gone after 30 days.kb syncGive the store a remote. Every machine shares it.- how do I install it?
You need Bun and git. There is no build step and no dependency.
installthree steps# a marketplace entry { "name": "kb", "source": { "source": "github", "repo": "jrnxf/kb" } } # in Claude Code /plugin install kb --marketplace <owner>/<marketplace> # ~/.claude/settings.json - kb replaces auto memory { "autoMemoryEnabled": false }
- /clear
SessionStart · kb context · the same 7,232 characters come back.
Give your agent a memory that fits.
Plain files. A fixed budget. Nothing lost at /clear.