Claude Code
Auto-save your Claude Code sessions
Coding sessions in Claude Code are hard to find again once the terminal closes. Setting up the Nokos CLI registers a Claude Code SessionEnd hook, so each session's JSONL log is sent to Nokos automatically. Nokos summarizes the session with AI and makes it fully searchable — when you did what, and how you fixed it.
What gets saved to Nokos
- Your prompts and Claude Code's responses (the full conversation log)
- Tool usage history (file edits, commands run, and so on)
- An AI-written session summary (what was done, decisions made, open items)
- Session date and working directory (stored per day)
Setup steps
Run in your terminal:
$ npx nokos setup
- 1
In a terminal with Node.js 18 or later, run the command below.
- 2
A browser window opens — sign in with your Nokos account to authorize.
- 3
Done. A SessionEnd hook is added to Claude Code's settings.json and future sessions are saved to Nokos automatically.
- 4
Open the Sessions page in Nokos to search and browse saved sessions.
Frequently asked questions
- When is a session sent to Nokos?
- At session end, via the SessionEnd hook. On Plus and Pro plans there is also a 30-minute periodic sync, so long sessions show up while they are still in progress. On the Free plan you can send manually with nokos push.
- Where does Claude Code store its conversation logs?
- Claude Code writes one JSONL file per session under ~/.claude/projects/. The Nokos CLI reads those files and sends them, so there is nothing to export by hand.
- Does it upload my source code or secrets?
- Only the conversation log (prompts, responses, and the record of tool calls) is sent. Repository files themselves are not uploaded. Everything stays in your own account, isolated by row-level security.
- How do I remove the hook?
- Run nokos disconnect to remove the hook. Sessions already saved remain in Nokos.
Start for free
Creating an account takes a minute. Saving and searching conversations works on the Free plan.
Start Nokos for free