Does oh-my-claudecode share memory across sessions?

oh-my-claudecode (OMC) orchestrates multi-agent workflows inside Claude Code, where each session and spawned worker starts with a clean context window. deja indexes the underlying Claude Code transcripts alongside every other harness on the machine so OMC sessions can recall prior fixes and decisions.

How do I wire deja into oh-my-claudecode alongside OMC?

Run deja install claude-auto (or deja install --auto to wire every installed harness). It configures Claude Code's MCP server, skill, /deja command, and lifecycle hooks without altering ~/.claude/.omc-config.json.

Will deja overwrite oh-my-claudecode rules in CLAUDE.md?

No. deja never modifies ./.claude/CLAUDE.md or ~/.claude/CLAUDE-omc.md; recalled context is injected on demand via hooks and the deja MCP tool.

Adding memory to oh-my-claudecode

cross-session and cross-agent recall for OMC orchestration inside Claude Code

oh-my-claudecode (OMC, also run via the omc CLI) orchestrates multi-agent runs inside Claude Code. Because OMC runs on top of Claude Code, each subagent invocation starts fresh and sees neither yesterday's orchestrator run nor fixes already settled in Codex, Cursor, or opencode. Pairing OMC with deja gives every spawned session searchable access to prior work.

Where OMC transcripts already live

OMC sessions write standard Claude Code JSONL transcripts under ~/.claude/projects/, while OMC keeps its own configuration in ~/.claude/.omc-config.json and rules in ./.claude/CLAUDE.md or ~/.claude/CLAUDE-omc.md. deja indexes Claude Code's transcript tree directly — alongside the other forty-six harnesses on the machine — without modifying your OMC setup or touching CLAUDE.md (why rules files grow).

Adding recall alongside OMC

deja install claude-auto

If OMC works next to Codex, Cursor, or other harnesses, wire all installed tools at once:

deja install --auto

On Claude Code, that registers the deja MCP server (recall, fix, blame, how, orient, context, remember, handoff), the deja-history skill, the /deja slash command, and the host lifecycle hooks (SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PreCompact, SessionEnd). Reversible with deja uninstall claude-auto.

What changes in a multi-agent run

Fresh worker cold starts: new OMC runs receive a compact project digest and relevant past fixes without bloating your system prompt or CLAUDE-omc.md.
Repeated shell errors and file context: before reading or editing a file, PreToolUse surfaces prior decisions recorded on that path; after a failed test or build command, PostToolUse returns the command that resolved the same failure before.
Compaction survival and handoffs: PreCompact carries active state past context resets, and handoff reads recent context produced by another harness on the same repo.

Local and scrubbed

The local BM25 store at ~/.cache/deja/index.db covers all forty-seven agent formats on the machine, including historical transcripts recorded before installing deja. Everything stays on disk, and tokens and credentials are scrubbed as transcripts are indexed.

Claude Code setup · Parallel sessions · Getting started · The Claude Code session format

Found this useful? Star deja-vu on GitHub.