These are the three shortest honest answers to "what does NEXO actually do?": one-command install, shared brain across clients, and review-gated public Evolution. All three stay compatible with the libre/open-source local-first story.
The primary route: install the runtime, detect clients, wire the same local brain, and check health immediately.
See why NEXO is more than an MCP endpoint: one runtime, one operator memory, and less fragmentation between Claude Code and Codex.
Understand the strongest unusual part of NEXO: opt-in self-improvement with Draft PRs, human maintainers, and pause/resume discipline.
If someone arrives from search instead of social, send them to the search-intent pages first.