Nexus is not another AI chat wrapper. It is a configurable runtime where models, agents, tools, permissions, context, sessions, workspaces, skills, hooks, plugins, and integrations are composable primitives.

git clone https://github.com/timothynn/Nexus.git
cd Nexus
cargo build --workspace
cargo run -p nexus-cli -- run "inspect this repository"

Launch the interactive operator console:

cargo run -p nexus-tui

nexus agents graph \
  research \
  implement:research \
  tests:implement \
  review:tests \
  --concurrency 2 --tools

• Provider-neutral models and streaming
• Bounded model-driven tool loop
• Filesystem and structured shell tools
• Permission policies and CLI approval
• Ctrl+C cancellation
• Audit events
• SQLite sessions and replay
• Git worktrees

• Layered configuration
• Repository discovery and context budgets
• Hierarchical instructions
• Git-aware context
• Code search
• Token estimates

Task Graph → Parallel Workers → Typed Handoffs
                              ↓
                     Supervisor → Reviewer
                              ↓
                     Explicit Human Review

Includes bounded concurrency, deterministic task layers, cancellation fan-out, cleanup policies, review candidates, explicit merge boundaries, container workspace foundations, CLI graph execution, and structured run-level events.

nexus-tui is now a dedicated terminal operator surface with a bidirectional runtime bridge:

Nexus runtime events ───────→ TUI timeline
                                  ↓
Operator command input ────→ command bridge
                                  ↓
                             runtime boundary
                                  ↑
Cancel control ────────────→ shared cancellation path

Current operator controls:

• Tab cycles focus
• ← / → switches workspace tabs
• ↑ / ↓ inspects the event timeline
• Enter dispatches the command input through the runtime bridge
• c requests cancellation outside command mode
• Esc leaves command input
• q exits

The TUI remains intentionally thin: it uses Nexus event contracts and a runtime command boundary rather than recreating orchestration inside the UI.

MCP Server → MCP Tool Adapter → ToolRegistry → Permissions + Audit

.nexus/skills/<name>/SKILL.md
.nexus/agents/<name>.toml
.nexus/hooks.toml

health check → provision → start → execute → stop → remove

Safe defaults: network disabled, read-only root, explicit workspace mount, configurable CPU/memory limits, and timeout enforcement.

plugin.toml → declared capability check → PermissionPolicy
     ↓
entrypoint containment → audited execution

apps/
├── nexus-cli/                 Scriptable operator surfaces
└── nexus-tui/                 Interactive terminal operator console

crates/
├── nexus-core/                Stable domain contracts
├── nexus-config/              Layered configuration
├── nexus-context/             Discovery, instructions, Git context, search
├── nexus-agents/              Scheduling, task graphs, coordinator, observability
├── nexus-models/              Provider contracts and adapters
├── nexus-tools/               Tool registry and local tools
├── nexus-permissions/         Policies and approvals
├── nexus-runtime/             Agent loop, cancellation, audit events
├── nexus-storage/             SQLite sessions and replay
├── nexus-workspace/           Worktrees + container lifecycle isolation
├── nexus-mcp/                 MCP client and Tool adapters
├── nexus-skills/              Skills, templates, and permissioned hooks
├── nexus-plugins/             Plugin discovery, runtime, capabilities, audit
└── nexus-sdk/                 Public embedding API

• Phase 1 — Execution Core
• Phase 2 — Context + Sessions
• Phase 3 — Multi-Agent Orchestration foundation

• MCP transport and Nexus Tool adapters
• Skills and templates
• Permission-controlled hook execution seam
• Plugin manifests and capability boundaries
• Public SDK foundation
• CLI integration for unified multi-agent orchestration
• Structured run-level observability
• Container lifecycle management
• Plugin runtime loading and capability enforcement
• Interactive TUI foundation
• Live runtime/event stream binding for the TUI
• TUI command dispatch and cancellation controls
• Tauri desktop application
• Remote workers

cargo fmt --all
cargo build --workspace --all-targets
cargo test --workspace
cargo clippy --workspace --all-targets -- -D warnings

Don't build an AI assistant that locks developers into one workflow. Build the primitives that let developers create their own.