Cross agent recall

Skill Lum1104/uni-code/skills/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").From its SKILL.md

Install

npx -y skills add Lum1104/uni-code --skill cross-agent-recall

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

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.