Kaectx — Development skill for Claude Code
Local searchable store of your coding-agent sessions (Claude Code, Codex), served to any agent over MCP.
How to install Kaectx
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open danPoku/kaectx and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Kaectx does
Local searchable store of your coding-agent sessions (Claude Code, Codex), served to any agent over MCP. Single Go binary, SQLite, everything stays on your machine.
Alternatives in Development
- Fast Jev Compaction — Claude Code plugin that replaces the compaction summary with Jev decisions: every tool call and result is scor 425 ★
- Claude Notifications Go — Cross-platform smart notifications -- 6 types, click-to-focus, context analysis, webhooks 365 ★
- Funes — Durable, searchable memory of your past agent sessions 349 ★
README
kaectx
*kaectx (formerly ctx). The command is still `ctx`.*
kaectx keeps one searchable copy of your coding-agent conversations, and lets any agent search it.
I use Claude Code and Codex on the same projects. Each one writes its own session logs, in its own format, and neither can see what the other worked out yesterday. Neither is good at searching its own history either. kaectx reads the logs those tools already write, puts them in a single SQLite file, and answers queries from a command line and from an MCP server, so an agent can ask "have we dealt with this before?" and get an answer from any agent's past sessions.
It is a single Go binary. Everything stays on your machine.
$ ctx search "how does the daemon embed new chunks in the background"
[claude-code] 2026-09-20T16:11:47.479Z claude-code:91ae043d-130e-4d25-8db5-266fe79bbbd5
User: run the embed worker from the daemon Assistant: Tests pass, inc…
Status
Early. The current release is v0.1.3. It has been run on one machine, on Ubuntu under WSL2; other platforms are untested. Expect breaking changes in the 0.x series, including to the database schema and the MCP tool output. See [Limitations](#limitations) before relying on it.
What it does
- Reads Claude Code and Codex CLI session logs and stores them in
~/.ctx/ctx.db. - Splits each session into retrieval units: one user turn plus the assistant's reply, with tool noise trimmed.
- Searches them by keyword (SQLite FTS5) and, if you run a local embedding model, by meaning too. The two rankings are combined with reciprocal rank fusion.
- Groups sessions into projects by the normalised git remote of their working directory, so the same repository checked out in two places is one project.
- Serves the history over MCP, so Claude Code, Codex, or any MCP client can search it, page through a session, and save notes.
- Redacts API keys and similar secrets before anything is written to disk.
- Can run as a daemon that ingests s
Related Skills
Bough
Visualize your Claude Code session history as a diagram of the work you actually did: days, tasks, prompts and
Farhand
Remote hands for coding agents: an MCP server that runs OpenCode / Claude Code / Codex work on a remote host o
Session Knowledge
Turn your Claude Code session history into a searchable local knowledge base — 13 MCP tools, pure stdlib, noth
Ocelin
Ocelin: a local Windows companion for Codex and Claude. Live sessions, app memory, conversation previews, sear
Harvest Memory
Promote durable learnings from the machine-local per-project memory store into the version-controlled repo mem
SessionAnchor
One-command context memory for Claude Code sessions. Local SQLite, zero dependencies.
Related Agents
Ade
Agent sessions routinely outlast the machine that started them, and checking a Claude Code or Codex run from a
Ollama Agent
Runs a local model served by Ollama on this machine. One mode - consult (no machine access; the endpoint is a
Claude Mem
A Claude Code plugin that automatically captures everything Claude does during your coding sessions, compresse