04INSTALL COCKPIT
One command handles the dependencies and enhancements. Then choose your AI provider, model, and sign-in method in Ares’s local wizard. Your keys never go through this website.
Install the latest Ares from RecursiveIntell, provision its dependencies, and build Desktop, voice, Rust bindings, Context Governor, local memory, ClaimLedger, Agent Graph, CEA, Pilot Bridge, and the current memory kit. Enhancements are included by default.
The installer fetches the latest Ares source, provisions managed Python and build tools, builds a managed runtime and Desktop, installs the Rust enhancements and memory kit, configures local memory and compaction, and opens the provider wizard. Required build failures stop the installation.
Use an API-key provider, a supported OAuth sign-in, or your own compatible local endpoint. Ares’s wizard owns credential storage. An OpenAI API key is needed only if you choose a feature that uses OpenAI’s API.
Ares uses ~/.ares. The installer preserves existing credentials, backs up configuration before changing it, and refuses to overwrite conflicting MCP mappings or unrelated launchers. On Linux with a user systemd session, its gateway starts after provider setup.
Agent Graph’s daemon needs a compatible provider configuration before remote graph execution. CEA and Pilot Bridge tools are installed; their jobs still need your workspace and data. Rerun this installer to update the full distribution. Use --no-desktop, --no-gateway, --minimal, or --skip-setup when needed.
Read the installer · Full setup and update guide · Ares source and provider documentation ↗
01 / MEMORY FOR OTHER AGENTS
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.
ONE DEVICE
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.
No Mnemes server copy, cross-device routing, or server-side recovery layer. Nothing about the underlying memory engine is downgraded.
02 / WHAT HAPPENS NEXT
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.
Recall fires and returns nothing. The agent continues normally.
Manifests, structure, dependencies, and README facts enter a namespace.
Conventions, failures, corrections, tasks, and evidence become searchable.
Later sessions retrieve why the current state exists instead of re-debating it.
03 / BEFORE YOU CONNECT DEVICES
A reachable server is not a synchronized memory system. Mnemes separates network, identity, shard, replica, route, retrieval, and receipt health.
Verify binary identity, one canonical data directory, embedding dimensions, integrity, and tools/list.
Verify loopback binding or an explicitly private proxy, device credentials, rotation, and revocation.
Verify distinct device identities, eligible shards, source provenance, temporal state, and route receipts.
Require freshness, offline backlog, idempotent replay, conflicts, source-offline retrieval, and recovery evidence.
04 / WANT THE SYSTEM ASSEMBLED?
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.
05 / GO TO SOURCE