cross-agent-recall

Recall the user's past coding-agent sessions across Claude Code AND Codex via uni-code. Use when the user references earlier work, a past fix, a decision, a command they ran before, or a session in another agent ("how did we fix X", "what did I try in Codex yesterday", "the approach from last week").

Jump to install

Repository: Lum1104/uni-code
Last source activity: July 16, 2026 at 14:17
Detected SKILL.md language: English
Stars: 7
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Lum1104/uni-code --skill cross-agent-recall

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Cross-agent recall

This machine has uni-code installed: a local, read-only index of every Claude Code and Codex session, exposed through the uni-code MCP server.

When to reach for it

The user references past work you don't have in context: "that bug we fixed", "the command from last time", "why did we choose X".

The user mentions another agent: "I started this in Codex", "Claude tried something yesterday".

You are about to re-derive something (a config, a fix, an investigation) the user has plausibly done before — one cheap search first can save the whole rework.

How to use it

resume_session when the user wants to CONTINUE earlier work in earnest ("resume the Codex session", "continue exactly where I left off") — it reconstructs the session's effective context: the source agent's own compaction summary plus everything after it. Pass project: "."; if the result turns out to be this very conversation, pass the other agent's name or an explicit id.

get_handoff for a quick one-page orientation instead (goal, where it ended, files touched, commands, errors) when the user just wants you up to speed, not a full continuation.

search_history with distinctive terms — code identifiers and error strings beat prose; Chinese/Japanese/Korean queries work. Add project: "." to scope to the current project.

read_session on the best hit's id. Default returns the END of the session (outcomes, conclusions); pass from_start: true to see the original goal.

list_sessions when there is no search term — e.g. "what was I doing yesterday?".

Notes

Results may come from a different agent than the current one; treat them as the user's own history, and say which agent/session an answer came from.

Everything is local and read-only; the index refreshes automatically on each query. If the very first query on a machine is slow, that is the one-time initial indexing.

If a search returns nothing, retry once with fewer or different terms before concluding the history doesn't exist.