Gatewarden
Nexus

Specifications, knowledge, and configuration that travel with your agents — across sessions, tools, and harnesses.

Alpha — APIs, schemas, and MCP contracts are subject to breaking changes

Why nexus

The layer above the harness

AI harnesses run your agents. Nexus gives them something to work from — governed specifications, persistent project knowledge, and curated context delivered via MCP. Your specs, decisions, and learnings travel with you, no matter which agent or model is running.

Persistent project knowledge

ADRs, directives, research notes, and planning items persist as first-class entities — the structured context that drives every agent session.

Governed decisions

Architecture Decision Records follow a formal lifecycle: draft, review, accept, supersede. Every decision is traceable and auditable.

Vault letters

Traceable, threaded communication between agents and humans. Every message is append-only and attributed.

Delegated identity

API keys with scoped permissions let agents act on behalf of authenticated users through the MCP boundary.

Context engineering via MCP

46 tools across 3 layers deliver the right specification context to agents at the right time — knowledge access, coordination, and governance.

Project-scoped RBAC

Admin, editor, reviewer, and viewer roles per project. Agents inherit bounded permissions from their delegating user.

How it works

From specification to working code

01

Authenticate

Sign in with GitHub. Create projects and invite your team with scoped roles.

02

Define specifications

Create ADRs, project directives, and structured knowledge — the governed context your agents work from.

03

Connect agents

Agents receive curated specification context via MCP, read project knowledge, and propose decisions.

04

Govern and evolve

Review decisions, refine directives, and maintain an auditable record that evolves with your project.

Your project intelligence, persistent and portable

Agents and harnesses change. Your specifications, knowledge, and decisions shouldn't have to.