Memory waits.
Recall fires and returns nothing. The agent continues normally.
04INSTALL COCKPIT
Use the hardware
that already fits.
Start with the full Hermes Agent (one command), install the memory engine at any boundary, or run a dedicated Mnemes server.
01 / CHOOSE THE BOUNDARY
Memory quality stays.
The deployment changes.
A single-device setup uses the same semantic-memory engine and retrieval stack. Mnemes adds the server copy, device identity, and routed cross-device layer. Node R1 adds setup convenience.
start here
ONE DEVICE
Agent Memory Kits
Install semantic-memory-mcp beside the agent you already use. Its memory stays on that machine and uses the same semantic-memory engine, hybrid retrieval, temporal state, provenance, and receipts.
WHAT THIS PATH KEEPS
- The same core memory and retrieval quality
- Local SQLite authority on your device
- Agent lifecycle integration through a host kit
BOUNDARY
No Mnemes server copy, cross-device routing, or server-side recovery layer. Nothing about the underlying memory engine is downgraded.
FULL AGENT STACK
One command. Complete AI agent.
Install Hermes Agent with Rust acceleration, 70+ skills, agent hooks, and 5 MCP servers — all pre-configured. Starts with a single curl command.
Full Josh's setup: llm-pipeline, context-governor, poly-kv, semantic-memory, agent-graph, claim-ledger, cea-graph, pilot-bridge, 70+ skills, 12 hooks. Use --help to see all flags. Skips Rust wheels: --skip-rust. Minimal: omit --with-josh-setup.
02 / WHAT HAPPENS NEXT
The quiet start
is correct behavior.
A new memory system should not fabricate a useful past. It begins empty, then compounds as the agent records durable project state and ingests the repositories you choose.
The codebase appears.
Manifests, structure, dependencies, and README facts enter a namespace.
Decisions accumulate.
Conventions, failures, corrections, tasks, and evidence become searchable.
Continuity emerges.
Later sessions retrieve why the current state exists instead of re-debating it.
03 / BEFORE YOU CONNECT DEVICES
Know which plane
you are proving.
A reachable server is not a synchronized memory system. Mnemes separates network, identity, shard, replica, route, retrieval, and receipt health.
Local memory
Verify binary identity, one canonical data directory, embedding dimensions, integrity, and tools/list.
Private reachability
Verify loopback binding or an explicitly private proxy, device credentials, rotation, and revocation.
Cross-device recall
Verify distinct device identities, eligible shards, source provenance, temporal state, and route receipts.
Replication claims
Require freshness, offline backlog, idempotent replay, conflicts, source-offline retrieval, and recovery evidence.
04 / WANT THE SYSTEM ASSEMBLED?
A custom node,
configured around you.
Node R1 runs the same Mnemes software you can install yourself. It is an early built-to-order option for people who need suitable hardware or want the server, agent environment, status display, and model boundary configured before arrival.
See the Node R1 concept →Discuss a custom build ↗Inquiry only. Final specification, battery, price, and availability are not yet committed.
05 / GO TO SOURCE