Chainabit NexusDeveloper documentation

A local-first workspace for command-line coding agents. Nexus runs them on your machine and exposes their shared surfaces — canvas, agent mesh, workspace files — through one local MCP server.

Quickstart

Install NEXUS, connect a hosted CLI as an MCP client, and make your first tool call.

Get started

Local MCP Server

nexus-mcp speaks newline-delimited JSON-RPC 2.0 over stdio and opens no network port. It serves the canvas_* and agent_* tool namespaces to any connected CLI.

Read the MCP guide

Canvas Collaboration

A shared surface an agent session can draw and edit on, visible to every other session and to you, in real time.

Explore the canvas

Agent Mesh

A local channel connected agent sessions use to hand off tasks and exchange messages, scoped to one workspace.

Read the mesh guide

Orchestration Governance

How concurrent tool calls from more than one agent session are sequenced, bounded, and kept from stepping on each other.

Read the model

Configuration & Paths

Where NEXUS keeps the per-session credential file a connecting CLI reads, and what permissions it carries.

See paths

Tutorials

End-to-end walkthroughs — draw a diagram from an agent, hand a task off between two agent sessions.

Start a tutorial

Reference

The exact protocol contract — request and response shapes, tool signatures, error codes, and version negotiation.

Open reference

Choose your path

New to NEXUS? Start with What is NEXUS?, then Install.
Connecting a CLI? Go straight to Connect a CLI and First tool call.
Building against the protocol? Read the MCP protocol reference and the MCP tools reference.
Want the shared surfaces? See the Canvas guide and the Agent mesh guide.
Curious why it's built this way? Read Local-first and Architecture.