Kage — AI skill for Claude Code
Local memory for AI coding agents.
How to install Kage
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open farmcan/kage and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Kage does
Local memory for AI coding agents. Find, replay, fork, bridge, and dispatch Claude Code, Codex, and Qoder sessions.
Alternatives in AI
- Claude Replay — Convert AI coding agent sessions (Claude Code, Cursor, Codex, Gemini, OpenCode) into self-contained, embeddabl 644 ★
- ZotSeek — AI semantic search for Zotero, with a built-in MCP server for AI agents (Claude Code, Codex) 193 ★
- Agf — Local-first TUI to find, search, and resume AI coding-agent sessions across Claude Code, Codex, Grok Build, Ki 148 ★
README
KAGE
Local memory for Claude Code, Codex, QoderCLI, and QoderWork.
[](https://github.com/farmcan/kage/actions/workflows/ci.yml) [](LICENSE) [](app/)
KAGE is the local memory layer for the AI coding tools you already run. Find the session where useful work happened, replay it, fork it, or bridge it into another agent's native resume format without uploading transcript content.
Your coding agents already have memory. KAGE makes it searchable, actionable, and local-first.
Homepage:
Latest release: [KAGE v0.2.1](https://github.com/farmcan/kage/releases/tag/v0.2.1)
Why Star KAGE
- One local surface for many agents. Claude Code, Codex, QoderCLI, and QoderWork keep separate transcript stores; KAGE makes them feel like one workspace.
- Task board for local agent runs. Dispatch one-off tasks, track queued/running/review/completed states, and keep the result visible without losing the session list.
- Mobile agent monitor.
kage servelets you see what local Claude, Codex, and Qoder runs are doing from your phone, with sessions first and dispatch as a secondary action. - Session memory without hosted indexing. Transcript content stays on disk by default; KAGE reads local files and launches local tools.
- Bridge and replay when context matters. Move useful work between agents or create a local HTML story replay for review.
What Works Today
| Surface | What you can do |
|---|---|
| macOS desktop | Browse project sessions, filter agents, inspect messages, start new sessions, launch Terminal.app, run resume/fork/bridge/replay actions. |
| CLI | Search |
Related Skills
Yalper
Record, replay, and debug AI coding agent sessions. Yalper snapshots your code at every agent step, finds the
Agit
git for running agents — inspect, replay, share, fork AI coding sessions
Agmsg Cmux Bridge
Bridges CLI AI agents (Claude Code, Codex, Gemini CLI, and more) over local SQLite with tmux/cmux/wezterm turn
Agent Session Bridge
Bridge local AI coding sessions between Pi, Claude Code, and Codex.
Elepha
Local session memory for Claude Code and Codex. Search your past AI coding sessions and recall them inside the
Bisect
Find the add-ons that bring your AI agent bug back. Repeatable checks, clear evidence, and a replay you can sh
Related Agents
Part 13: Memory Bridge (Give Coding Agents Your Brain)
When you spawn Codex or Claude Code to build something, they start blind. They don't know your architecture de
Opencode
Coding subagent that runs inside opencode, on any provider and model opencode supports (OpenAI, Google, Moonsh
Ade
Agent sessions routinely outlast the machine that started them, and checking a Claude Code or Codex run from a