If something here reads like a limitation, it probably is one. Kinjot is built light, on purpose. We’d rather explain the trade-offs before you sign up.
A solution notebook for AI-assisted developers. When Claude Code or Codex produces a fix, command, or explanation worth keeping, tell your agent “jot that down”. Kinjot saves the useful result as an ordinary Markdown note you can search, organize, and export without keeping the whole conversation.
No. Local mode requires no account: notes persist in your browser but do not sync. Export anything you want to keep. You can move the local library into an account later for sync.
Yes. Import Markdown files or a Kinjot zip; nested paths become folders, and supported front matter carries over. Recognized creation dates are preserved, but modification dates are not, so imports appear recently updated. Export one note as Markdown, selected notes as plain files, or the whole library as a zip.
Mostly. After one successful online load, local mode opens, reads, searches, and writes offline. A signed-in workspace does the same on a browser you’ve signed into before. Signed-in edits save immediately and sync when the connection returns. If the same note changes in two places, the second version is preserved as a conflicted copy; Kinjot never merges text away. An expired session also leaves notes editable until you sign in again. The editor shows whether changes are synced, waiting, or need review.
Under 100 ms at 2,000 notes. Every release must pass a test enforcing that limit. Search runs entirely in your browser, indexes titles and bodies, and is free on every plan.
Free includes notes, folders, tags, title-and-body search, MCP and CLI capture, Markdown editing, sync, import and export, optional version history, and bring-your-own-key Recall. See pricing for the full comparison.
Hosted Recall is a Pro feature: it retrieves relevant notes by meaning and answers from them. Free and Pro users can instead provide an OpenAI or Anthropic key. The key stays in browser memory for the session, and answers are not saved to hosted Recall history.
Pro includes one monthly pool of 500 AI credits, shared by Recall, Kin chat, Tidy and cloud dictation. Each action costs what it uses, and Settings shows your usage, what is left and your reset date. The pool resets on your renewal date, not the first of the month, and unused credits don’t roll over. Stopping keeps the credits already used; a request the AI provider never received costs nothing. Searching your Recall history and on-device dictation don’t use credits.
Version recording is Free and on by default for new accounts; you can turn it off in Settings. You can compare and restore recorded versions. The full flow works offline in local mode; signed-in browsing requires a connection.
Nothing is deleted. Your notes, folders and tags are untouched, and past recall answers stay readable forever. Cancelling keeps Pro through what you’ve already paid for.
Our infrastructure encrypts notes at rest and in transit, but they are not end-to-end encrypted. E2EE would prevent server-side Recall. Treat Kinjot like a notebook, not a vault. Don’t jot secrets.
On a hosted Pro account, the AI features send what each needs, and never a note in a No AI folder. Voyage AI receives note text when a note changes, to index it for meaning-based search, and the queries Recall and Kin chat search with; a language model from Anthropic or OpenAI writes a one-line gist of each note. Recall sends relevant note material to the services used for retrieval and answering. Tidy sends note titles, gists, and folder and tag names (a note body only when no current gist exists). Kin chat sends your conversation, the notes and Inbox items Kin reads, and the note you have open (its text when it is 12,000 characters or less, otherwise its title), with your local time and time zone, to Anthropic or OpenAI. Cloud dictation sends only the recording to OpenAI for transcription, through Kinjot, which keeps no copy. On any plan, bring-your-own-key Recall sends your query and up to four matching note excerpts directly from your browser to OpenAI or Anthropic, and, in a signed-in account, own-key dictation sends the recording directly from your browser to OpenAI. Your provider key stays in memory for the session and is not stored by Kinjot. On-device dictation sends nothing.
It moves to Trash, restorable until you empty it. Emptying trash erases the note’s AI embeddings and gists immediately; a residual copy of the text remains in the database until you close your account. Deleting your account hard-deletes every row, no soft copies left behind.
Automated tests try to access other users’ data on every change. A policy alone is not evidence; the attack itself must fail. API keys are stored as hashes and shown once. No ads, no data selling, no tracking cookies.
Two commands. Install the package and add your key with kinjot key, then register it:
Claude Code and Codex are the ones we test against; anything that speaks MCP should work. There’s also a plain CLI for your own terminal, including stdin piping: cmd | kinjot add "title".
No. Search returns at most five compact hits and never includes note bodies. A body enters the conversation only when the agent fetches that note. IDs are shortened, dates truncated, and summaries capped.
No. The tools are built so agents only save when you say “jot that down” or similar. An agent should never decide on its own what’s worth remembering, and the MCP server is open source (MIT) if you want to check. The same goes for changing a note: an agent edits or appends only when you ask it to and name the note, and every change it makes through the MCP tools to a note’s text is kept in that note’s history. An append sent from the CLI with --no-snapshot, which any of your keys with Full access can send, follows your own history setting instead; an append never removes anything. The one thing an agent may do unasked is send a short message to your Kinjot Inbox when it stops with a question, a blocker or work left for later; it never saves a note that way.