Solve
Work through the problem with Claude Code, Codex, or the tools you already use.
A solution notebook for AI-assisted developers
You already solved this once. Keep the fix.
Your agents do great work. When Claude Code or Codex produces something worth keeping, say “jot that down.” Kinjot saves the result as a searchable note, not the whole conversation.
NO ACCOUNT NEEDED FOR LOCAL MODE · WORKS WITH CLAUDE CODE & CODEX
All notes4
+ New note
Search notes…⌘K
Start here: how to use Kinjot
Kinjot is where your AI coding agents' output goes so it doesn't vanish when the session ends.
Magic links over passwords: a decision log
MEMORY.md gets the one-liner; the actual reasoning lives here so future-us doesn't relitigate it.
Why the JWT kept expiring in dev
Root cause from tonight's debugging session, saved before I forget: The dev container's clock drifted 4 minutes ahead of the host.
Restore staging from a snapshot: the exact incantation
The sequence from today's incident, with the flags that actually matter: aws s3 cp s3://acme-backups/pg/nightly…
Why the JWT kept expiring in dev
Root cause from tonight’s debugging session, saved before I forget:
- The dev container’s clock drifted 4 minutes ahead of the host.
- Tokens minted by the auth server were “issued in the future”, so the client library treated them as invalid and silently refreshed on every request, which looked like instant expiry.
- Nothing was wrong with the token TTL config we spent an hour on.
Fix: wsl --shutdown (or restart the container) to resync the clock. Detection for next time: compare iat in the decoded token against Date.now(). A negative age is always clock skew.
94 words
One small habit
Solve it. Jot it down. Find it later.
Good answers should outlive their conversations. Kinjot keeps the loop short.
Jot
Tell your agent to jot down the useful result. You decide what becomes a note.
Find and use
Find the note in Kinjot, or ask your agent to retrieve it when the problem returns.
The conversation can be long. The note does not have to be.
Save the result, not the transcript
What you’ll actually need again.
Save the final fix, exact command, configuration detail, or explanation that made the bug make sense.
A fix – The change that worked, with enough context to recognize the problem next time.
A command – The exact invocation you do not want to reconstruct from shell history.
A snippet – The small piece of code or configuration worth reusing.
A decision – What you chose, what you rejected, and why.
An explanation – The non-obvious reason the system behaved that way.
A setup guide – The steps you will forget before the next clean install.
A failed approach – The tempting path that already wasted an afternoon.
A checklist – The sequence that makes a fragile task repeatable.
Deliberate by design
Manual is the quality feature.
Kinjot doesn’t watch conversations or guess what matters. You choose what to keep, and your agent saves it.
Manual capture keeps the notebook useful: no automatic transcripts, background capture, or half-finished reasoning to clean up.
You choose what survivesCapture happens only when you askNotes stay separate from the conversation
› it worked, jot this
● kinjot · jot (MCP)
⎿Jotted “Postgres pool exhaustion after launch” (id 7c2f3a9e…, tags: db, infra, acme-api).
Saved to Kinjot with tags: db, infra.
Less captured. More worth finding.
Find comes before AI
Search when you know the words. Ask your notes when you don’t.
Search titles and bodies for free. Use Recall when you remember the problem but not what you called it.
Search · Free
Use the words you remember.
Search runs in your browser across loaded note titles and bodies, excluding Trash.
poolESC
Notes · 2 matches
Postgres pool exhaustion after launch
early return skipped client.release() so the pool drained…
Connection pool sizing cheatsheet
max = cpu × 2 + effective_spindle_count
Recall · Pro or your own key
Describe what you mean.
Hosted Recall finds relevant notes by meaning and answers from them. Any tier can instead use a session-only OpenAI or Anthropic key.
‹Recall
Minimize⤢×
›why did every request freeze once traffic spiked?↵ Ask
Matchesvoyage · 214 notes
Postgres pool exhaustion after launch89%Load test runbook51%
Answergpt-luna
A handler opened a transaction and returned early on validation errors without releasing the connection. Under load the pool drained, so every new request just blocked waiting for a free one. Slow queries were not the problem.
Fix: release the client in a finally, and cap the pool below Postgres’s max_connections.
Postgres pool exhaustion after launch ↗
Without a provider key, local-mode Recall finds matching notes but cannot generate an answer.
In the workflow you already have
MCP that stays out of the way.
The kinjot npm package lets Claude Code, Codex, and other MCP clients save, retrieve and update notes without taking over your workflow.
jotsave a Markdown notefind_jotsfind notes by keywordrecall_jotsfind notes by meaning where availableget_jotread one notelist_recent_jotslist recently updated notesedit_jotchange a note you nameappend_to_jotadd to a note you nameFirst-time setup
npx kinjot keyclaude mcp add kinjot -- npx -y kinjotcodex mcp add kinjot -- npx -y kinjot› check jots, why are requests freezing under load?
● kinjot · recall_jots (MCP)
⎿Closest jots by meaning:
- [0.89] Postgres pool exhaustion after launch — early return skipped client.release(); the pool drained under load
- [0.42] Load test runbook — k6 ramp profile + how to read the p99
First one looks like a match, want me to read it?
Product quality
Built light, on purpose.
Kinjot keeps everyday work fast and quiet. Search runs in your browser, common actions have keyboard shortcuts, and the interface stays focused on the note.
Yours to take anywhere
Keep your notes without committing to Kinjot forever.
Import Markdown, export individual notes, or download your entire library. Your notes should remain useful even if you stop using Kinjot.
Export first. When you delete your account, Kinjot hard-deletes its stored account data.
Useful, but not the headline
A better notebook still needs guardrails.
Version history · Free
Recording is off by default. Enable it to browse and restore versions; signed-in browsing requires a connection.
Tidy · Pro
Tidy organizes notes with folders and tags. Ask it to and it will propose new titles too — titles only, never the body of a note, and never without showing you first. It cannot delete notes or delete folders.
Automation gets boundaries. Nothing changes without you seeing it first.
Version historyCLOSE
Yesterday 4:10 PMPostgres pool exhaustion after launch
Yesterday 2:52 PMPostgres pool exhaustion after launch
Jul 9, 9:20 AMProd outage — first notes
This version
Cause: the connection pool drains under load.
Fix: bumped max_connections to 500.
Current
Cause: the connection pool drains under load.
Fix: release the client in a finally block.
Detection: watch pool.waitingCount climb first.
Why Kinjot exists
I built Kinjot because I kept losing my agents’ best output. The solution was rarely worth saving as an entire conversation, but the final fix, command, or explanation usually was.
A notebook, not a vault
Kinjot is not end-to-end encrypted. Keep passwords, private keys, and other secrets somewhere designed for them. Hosted and bring-your-own-key Recall send matching note material to the providers used to retrieve or answer your question.
Local mode doesn’t sync and needs one successful online load before opening offline. Clearing site data can erase the notebook, so export anything you want to keep.
Keep the answers worth keeping
Lose fewer good answers.
Build a compact library of useful fixes, commands, and explanations.
NO ACCOUNT NEEDED FOR LOCAL MODE · EXPORT ANYTIME