Omni-Mem — Cross-Session Memory Bridge

Omni-Mem is a lightweight memory bridge for agentic development. Using just two hooks and a JSON state file — with zero new services to run — it surfaces context across concurrent Claude Code sessions on the same machine, telling each new session what other sessions were working on. It was built to keep multi-agent and multi-session workflows coherent without standing up infrastructure.

Problem

When several Claude Code sessions run in parallel on one machine, each one starts cold. A session spinning up to continue a task has no idea that another session is mid-flight on a related piece of work, which leads to duplicated effort, conflicting edits, and context that resets every time a new terminal opens. The conventional fix is to stand up shared infrastructure — a memory service, a database, a coordination layer — which is heavy machinery for what is fundamentally a handoff problem.

Approach

Omni-Mem keeps the surface area deliberately tiny. The whole bridge is two Claude Code hooks backed by a single JSON state file:

• One hook writes — a session records what it is working on as it starts, dropping a compact entry into the shared JSON state.
• One hook reads — a new session picks up that state on launch, so it enters the world already aware of what sibling sessions are doing.

No daemon to run, no database to provision, no network endpoint to secure. The JSON file is the entire coordination substrate, and Claude Code's native hook system is the only runtime. The constraint is intentional: the moment a tool requires operators to maintain infrastructure, it stops being a lightweight bridge and becomes a product.

Outcomes

The result is a memory bridge that fits inside two hooks and a state file, runs entirely inside the Claude Code runtime, and introduces zero new services to operate. Multi-session workflows get cross-session context for free, and the footprint is small enough that the coordination cost never competes with the work it is coordinating.