nexus-prime

v7.10.14

Published

15 days ago

Local-first memory and orchestration for AI coding agents—carry decisions, constraints, relevant scope, and verification across Claude Code, Codex, Cursor, and other MCP clients.

Install from npm · Read the docs · Compare · Start a pilot →

Nexus Prime is a local-first memory and orchestration layer for coding agents. It keeps useful work moving across Claude Code, Codex, Cursor, Windsurf, OpenCode, Aider, and other MCP-compatible tools—without making you rebuild context at every handoff.

Quick start

npm install -g nexus-prime
nexus-prime setup all
nexus-prime start

Open http://localhost:3377, then keep using your coding agents as normal. Nexus Prime supplies the shared workspace context underneath them.

Auto-bootstrap runs on first non-bootstrap call, so a configured client can recover the workspace contract without another setup pass.

Requires Node.js 20+ on macOS, Linux, or Windows.

The handoff Nexus Prime preserves

Most agent failures are not model failures. They happen when settled work disappears between sessions or tools.

| Source agent finishes with | Nexus Prime carries | Receiving agent begins with | |---|---|---| | Diagnosis or plan | Objective and accepted decisions | The next bounded action | | Relevant files and constraints | Ranked scope and project rules | The right part of the repository | | Tests run and open risks | Verification state and next check | Evidence instead of a transcript |

The next agent gets the decisions—not the entire chat history.

What changes after install

Work survives the tool switch. Move between agents without restating the objective, settled choices, and relevant scope.
Context stays bounded. Nexus ranks files and durable memories before broad repository reading.
Execution stays inspectable. Plans, routes, worker state, verification, and handoffs remain visible.
Memory becomes useful work context. Accepted preferences and project facts can inform later runs instead of living in disconnected chats.
Your existing agents remain your agents. Nexus Prime coordinates the workflow underneath them; it does not replace them.

Where the handoff matters

Incident diagnosis → tested patch
Requirement clarification → reviewed release
Dependency map → next migration batch
Evaluation finding → bounded orchestration fix
Repository map → first scoped contribution
Discovery brief → implementation with open decisions visible

Proof you can inspect

Nexus Prime is designed to show its work. The local dashboard exposes the context selected, memory recalled, run state, token telemetry, and verification status available for a task.

In the August 1, 2026 20-file planning fixture, the bounded Nexus plan used 5,695 estimated input tokens instead of the 19,035-token naive-full-read baseline (3.34×). That is one local measured fixture—not observed provider billing savings or a universal claim. See docs/investor/benchmark-results.json and use your own dashboard to judge the result on your repositories.

An independent technical review also installed the package and checked the CLI and MCP path.

Competitive position

Nexus Prime sits beneath the coding agents you already use: a local control plane for continuity, bounded context, and reviewable execution evidence. See how that position differs from adjacent tools →

Works with your stack

Configure everything with nexus-prime setup all, or target one supported client with nexus-prime setup <client>.

Agent integration contract

For explicit MCP integrations, start a work session with:

nexus_session_bootstrap — recover relevant workspace context and operating rules.
nexus_orchestrate — route the raw request through the selected skills, workflow, budget, and verification gates.

Nexus Prime can then narrow context, preserve decisions, and leave a handoff for the next agent.

Start a pilot

Bring one handoff your engineering team repeats. We will:

map where the work changes hands;
connect the coding tools already in the workflow;
define the outcome, guardrails, and evidence the pilot must produce.

Start a Nexus Prime pilot →

Privacy

Nexus Prime is local-first. Workspace memory, run state, and operational context live on your machine. Optional telemetry is off by default and should never include source code or memory contents.

Published

Vulnerabilities

Links

Maintainers

Keywords

Readme