Structured state
Built to keep agent state explicit across long execution windows.
Built for OpenClaw integrations
Deterministic memory
for long-running agents.
ClawCapsule is a local-first memory runtime design for structured state, content-addressed artifacts, deterministic Context Bundle compilation, and checkpoint/restore semantics.
Current public validation is bounded. Start with the evidence page for the frozen proof surface.
)What It Is
Content-addressed artifacts
Artifacts are hash-addressed for integrity and reproducibility.
Deterministic Context Bundle compilation
Same state + same compile request produces identical `bundle_text`.
Checkpoint and restore
Checkpoint validation enforces integrity and fails closed on mismatch.
Local-first durability
Crash-safe persistence is applied at commit boundaries in release mode.
)Evidence
Current bounded evidence pack
The live evidence page is the current public source of truth for validation scope, supporting reports, and release-boundary reading.
)Why Determinism Matters
- Same state + same compile request -> identical memory context.
- Repeatable runs enable reliable debugging and evaluation.
- Restart continuity without re-onboarding.
- Strict budgets prevent prompt bloat and drift.
- Traceability via artifact hashes.
)How It Fits With OpenClaw
1) OpenClaw emits memory events
The runtime surface is designed to accept durable state updates.
2) ClawCapsule compiles Context Bundle
The compile path is designed to return deterministic `bundle_text`.
3) Agents resume from stable state
Checkpoint and restore semantics support bounded restart continuity.
Current public validation of this path is bounded; see the evidence page.
)Who This Is For
- OpenClaw users running long sessions where memory drift hurts outcomes.
- Agent builders who need reproducible behavior for testing and evals.
- Teams that want durable local memory without a hosted service dependency.
)Quick Start
ClawCapsule runs as a local daemon. In release mode it is loopback-only HTTP. Do not bind it to a non-loopback address.
This quick start is for macOS/Linux shells.
Release-mode runtime quick start
# 0) Get the repo
git clone https://github.com/shaunjones123/clawcapsule
cd clawcapsule
# If you already have it locally:
# git pull origin main
# 1) Build the release binaries
cargo build --release
# 2) Set up release-mode runtime config
export OCM_MODE=release
export OCM_STORAGE_ROOT="$PWD/.ocm"
export OCM_RELEASE_KEY_HEX="$(openssl rand -hex 32)"
# 3) Start daemon
./target/release/runtime-daemonOpen a second terminal in the same repo and verify the daemon is healthy:
Health check
cd clawcapsule
curl -s http://127.0.0.1:7337/v1/healthA healthy daemon returns JSON with status set to ok.
What the release key line does
Release key
export OCM_RELEASE_KEY_HEX="$(openssl rand -hex 32)"This generates a new 32-byte release key and stores it in the environment as 64 hex characters. Release mode requires this key and will fail to start if it is missing or invalid.
If you want to keep using the same storage root across restarts, reuse the same OCM_RELEASE_KEY_HEX value.
OCM_STORAGE_ROOT="$PWD/.ocm"stores ClawCapsule state in a local.ocmdirectory inside the repo.- In Unix release mode, the daemon uses
127.0.0.1:7337by default. - The main quick start ends at daemon startup and
/v1/healthverification.
)Public Review
Start with the current public surface
For reviewers, the right path today is the live evidence page plus the public GitHub repo root. Read implementation and release claims conservatively against that bounded surface.