Every Claude Code or Codex session produces something worth keeping: the reason the bug happened, the command you’ll need in three weeks. Then it’s gone. Kinjot exists so “jot that down” is all it takes to keep it.
Deliberately small. Not a second brain. A notebook that sits next to your agents and gives things back when you ask.
Agents only jot when you tell them to. An agent that silently decides what to keep is building someone else’s notebook. Every jot is explicit. There’s no background capture.
Search under 100 ms at 2,000 notes is a test our releases must pass. Tenant isolation is verified by automated attacks in CI, not by a policy document. If we can’t enforce a promise in code, we don’t make it.
Export is one click and produces real folders of markdown with YAML frontmatter, readable by Obsidian or anything else. Deleting your account hard-deletes every row. Lock-in is not a retention strategy.
No end-to-end encryption, no sync in local mode, and imported modification dates are not preserved. Real limitations, listed on the FAQ instead of buried. We’d rather lose a signup than surprise a user.
The free plan is the product. Pro covers the AI bills and funds development.
Kinjot is built and run by one person. I got tired of losing good session output, so I built the notebook I wanted. It’s open in a tab next to my terminal right now.