Most memory servers have one store and one retrieval path, so 'what were we doing an hour ago' and 'what rule did we agree months ago' compete in the same index. Here they are separate layers with different lifetimes: hot context expires, durable memory consolidates. The protocol side is opinionated in a way worth knowing before you install — a task closes with an outcome, evidence and the files it touched, and strict mode will block a write when no task is open. That suits people who want the discipline enforced, and will annoy people who do not.
The local runtime core behind NEXO Desktop: a memory and execution layer that keeps an assistant's context, tasks and learnings on your own machine and shares them across clients.
- nexo_remember and nexo_memory_recall — durable memory for rules and decisions you want kept
- nexo_consolidate, which turns accumulated memory into a bounded set of insights rather than an ever-growing pile
- A hot context layer separate from long-term memory: nexo_pre_action_context, nexo_recent_context, nexo_recent_context_capture, nexo_recent_context_resolve and nexo_hot_context_list
- A 24-hour freshness window by default, configurable per call up to 168 hours, so an active topic stays live across new chats, different clients, cron ticks and email processing
- Topics carrying an explicit state — active, waiting on you, waiting on a third party, blocked, resolved or abandoned
- nexo_task_open and nexo_task_close, where closing requires an outcome, the evidence and the files changed
- Protocol strictness you choose: lenient warns, strict blocks writes with no open task, learning blocks with an explanation
- nexo_run_workflow for durable multi-step execution with open, update, resume and replay
- nexo_guard_check, nexo_learning_add, nexo_startup and nexo_heartbeat for the runtime around all of it
- Nexo doctor for diagnostics, plus Skills, Watchdog, followups and Deep Sleep
Installed with npx from nexo-brain, which sets up the runtime, configures the MCP server and wires the shared brain into supported clients; a Docker path exists for a persistent container. Memory lives in local SQLite on your machine. NEXO Desktop is the supported product surface for downloads, billing and support — this repository is the runtime core it bundles, and the nexo-brain package and binary names remain for install and update compatibility rather than as a separate product.
One command — npx nexo-brain init