Organize session notes, snippets, and artifacts into scratchpads — a folder + manifest — with a read-only visual viewer. Just files on disk, no central store, no lock-in.
A scratchpad is just a folder containing scratchpad.json — the folder path is its identity. There is no central store.
scratch is a thin metadata layer over the filesystem: it initializes pads, prints how to use them, and registers files you create. You write and edit files with your normal tools — the CLI never authors, copies, or moves content.
Agents generate a lot of temporary knowledge per session — notes, snippets, command output, intermediate artifacts — and it has no home. It ends up scattered across the repo, buried in chat history, or lost when the context window rolls over.
A scratchpad gives that working memory a deliberate place: a folder + scratchpad.json manifest, kept out of your source tree, that captures what each file is and why it exists.
Requires Bun — scratch runs on the Bun runtime.
bun add -g @nikiforovall/scratchpad # exposes the `scratch` commandThen head to the User Guide.