Local stores
Separate transcriptsEach agent keeps its own files and resume rules.
.claude.codex.qoderLocal-first session memory
Find, review, fork, and bridge AI coding sessions across Claude Code, Codex, QoderCLI, and QoderWork without uploading transcript content.
curl -fsSL https://raw.githubusercontent.com/farmcan/kage/main/install.sh | bash
KAGE does not need a hosted index to feel useful. It reads what your tools already write, groups it by project, then prepares explicit actions you can run.
Each agent keeps its own files and resume rules.
.claude.codex.qoderDirectory first, then agent, date, title, and transcript text.
textagentsidecarKAGE prepares commands and exports; you decide what runs.
nativebranchc2xUse CLI, desktop, or trusted LAN monitor without sending transcripts away.
scriptreviewLANInstall KAGE, check which local agent stores it can see, then list or search the sessions already on your machine. Bridge only when you are ready to continue context in another agent.
This downloads the repo package, installs the global kage command, and keeps transcripts local.
curl -fsSL https://raw.githubusercontent.com/farmcan/kage/main/install.sh | bash
Use doctor first if you are not sure whether Claude Code, Codex, or QoderCLI sessions exist locally.
kage doctor
Start with a small recent window, then open the desktop app when you want the visual workspace.
kage sessions --since 30d --limit 20
Search transcript text first; when a Claude session should continue in Codex, run the bridge.
kage search "auth" --limit 10
kage c2x
Agent transcripts are already on your machine. KAGE turns them into local project memory you can search, inspect, continue, and move between tools.
Skip raw JSONL folders and jump back to the session where the useful decision happened.
Continue Claude Code work in Codex, move Codex context to QoderCLI, or keep lineage sidecars for audit.
KAGE scans local agent stores and exposes desktop, CLI, and trusted LAN workflows around them.
Use this path for scripting, bridge commands, session search, and local web monitoring.
curl -fsSL https://raw.githubusercontent.com/farmcan/kage/main/install.sh | bash
Browse sessions, filter agents, inspect context, and run explicit resume or bridge actions.
The current DMG is unsigned. If macOS blocks first launch, right-click KAGE.app and choose Open.
KAGE should earn attention by doing useful local work first: find sessions, inspect context, and move memory between agents only when you ask it to.
Use project scope as the main mental model, with Codex, Claude, QoderCLI, and QoderWork filters when needed.
Search titles, recent prompts, transcript text, and dates so you can choose the right memory instead of guessing.
KAGE prepares native commands and exports; launching or changing a live agent still stays explicit.
KAGE does not replace Codex, Claude Code, or QoderCLI. It gives you the missing local layer for discovery, cleanup, replay, and target-native bridge exports.
Directory is the primary context; agent filters help separate Codex, Claude, QoderCLI, and QoderWork.
Actions are explicit, previewable, and backed by CLI JSON so the app stays a thin local shell.
See what local agents are doing from phone or tablet without turning KAGE into cloud sync.
Cross-agent exports use target-native UUID session ids and keep source lineage in sidecars. The command you get is the command you run.
| Route | Use it when |
|---|---|
kage c2x |
Continue a Claude Code session in Codex. |
kage x2c |
Move useful Codex context into a Claude Code resume file. |
kage x2q |
Bridge a Codex session into QoderCLI with a matching sidecar. |
kage sessions --since 90d --limit 120 |
List a bounded recent session window for large local histories. |
kage serve --password 1234 |
Open the local web monitor for a trusted phone or tablet. |