NEXO Brain
# NEXO runtime core
This repository contains the local runtime core that powers NEXO Desktop.
NEXO Desktop is the public product and the supported user-facing installer,
update channel, onboarding surface, settings UI, and support path. The legacy
`nexo-brain` package and binary names remain temporarily for install/update
compatibility only; they are not a separate product line.
## Current contract
- Version `7.38.7` is the current packaged-runtime line
- Public product: NEXO Desktop
- Runtime role: local NEXO core bundled with Desktop
- Active systems: local memory, Deep Sleep, Evolution support-ticket mode,
Skills, Watchdog, followups, doctor diagnostics, and MCP tooling
- Evolution mode: enabled by default for Desktop-managed installs; it never
opens GitHub branches, pushes, PRs, transcripts, local databases, or raw
private evidence, and routes product-improvement requests through sanitized
support tickets
- Distribution: Desktop installers and update manifests are published through
the NEXO Desktop release channel
Use [nexo-desktop.com](https://nexo-desktop.com) for downloads, billing,
support, and product information.
## Client parity
Release changes that touch bootstrap, session handling, Deep Sleep, client
sync, or shared runtime claims must also keep `docs/client-parity-checklist.md`
current.
- Managed via bootstrap + Codex config `mcp_servers.nexo`
- Managed MCP-only shared-brain metadata
- Runtime doctor parity audit
TDQS
Scored across 170 tools
Every tool has a distinct resource+verb (get/update/delete/list by entity), but with 170 overlapping entities there is inevitably semantic overlap (e.g. multiple 'explain' or 'surface' tools); still, each appears to target a unique function.
Uniform nexo_ prefix with snake_case verbs and nouns is extremely consistent across all 170 tools; pattern is predictable.
170 tools is an extreme surface area. Even intentional 'mission control' servers rarely need this many; it overwhelms context and decision-making.
For the apparent domain (multi-session memory, checkpoints, events, sessions, products, external APIs), lifecycle coverage is thorough — create/update/close/query pairs exist across the board. Some areas (e.g., plugin removal edge cases) may still have gaps, hence not 5.