Portable memory across the runtimes you already use.

Five integration modes

Each adapter is classified by the deepest mode it can safely support, and degrades cleanly to a shallower mode when the runtime does not expose a stable seam. A runtime that starts as observe-only can grow augment, piggy-back, and replace paths over time without changing the core memory model.

Replace

UrBrain becomes the runtime's primary memory provider through an exposed provider seam.

Maximum portability. Memory lives in one place across every runtime a team uses.

Piggy-back

UrBrain mirrors or subscribes to the runtime's built-in memory while it keeps using its own.

Low risk. Native runtime behavior is preserved while a portable copy is built up alongside it.

Import / export

UrBrain migrates memory in and out of a runtime in a stable exchange format.

Onboarding and exit are explicit, not lossy. Switching runtimes does not reset a team's history.

Augment

UrBrain injects retrieved context through the runtime's prompt or context surface.

Smallest integration footprint. Useful even when no deeper memory seam is exposed.

Observe only

UrBrain captures transcripts, events, and artifacts without affecting live memory.

Safest fallback. Provenance and recall are still established for later replay and audit.

The first wave

The runtime adapter roadmap covers the agent stacks the team uses and observes most closely. Coverage progresses from augment through piggy-back to replace as each runtime's seams stabilize.

• OpenClaw & Pi. The richest target. OpenClaw embeds Pi for provider, tool-call, and coding-agent runtime behavior, so the adapter treats Pi state as part of the runtime surface and aims for replace or piggy-back through the memory/context/plugin seams.
• Hermes. A strong test case for replace-mode memory. Hermes has source-aware sessions and cross-platform continuity; if its provider seam stays stable, UrBrain can delegate memory to it directly.
• Claude Code. Hosted MCP works on day one for augmented retrieval. Durable import of transcript, task, and sidechain state makes the operator's history portable.
• PicoClaw & Lossless Claw. JSONL transcripts, EventBus hooks, and compaction artifacts feed UrBrain as evidence. Session-family retrieval is preserved, not flattened.
• Paperclip & NemoClaw. Coordination and host platforms. UrBrain ingests work context — org chart, goals, issues, runs, blueprint state — as provenance, not as a memory backend.

Stable IDs, exportable history

Adapters preserve external identifiers — session IDs, event IDs, artifact hashes, runtime-native memory IDs — on every record. That makes deletes, exports, and replays addressable in the runtime's own vocabulary, and makes a future migration to or from any of these systems an explicit operation rather than a forensic project.