Synaptory™ Synaptory™ Get Started
First governed Cycle

Get started with Synaptory™

Install Synaptory in Claude Code, Codex, or Cursor, then use the SPQ lifecycle to move a bounded outcome through Discovery, Commit, Cycle Execution, Sync, Checkpoint, and Acceptance.

Claude Code

Full host-native integration through the Synaptory marketplace.

/synaptory

Codex

Standard, non-regulated SPQ on Codex CLI 0.147.0 or newer.

$synaptory

Cursor

IDE and headless paths with project rules, agents, hooks, and MCP.

SPQ certified

1. Install the shared CLI

One CLI installation handles identity, project access, skills, policy, diagnostics, and optional runtime operations for every host.

# macOS / Linux
curl -fsSL https://synaptory.h3t.co/cli/install.sh | bash

# Windows PowerShell
iwr -useb https://synaptory.h3t.co/cli/install.ps1 | iex
synaptory login
synaptory whoami
synaptory projects list

Use synaptory login --device on a machine without a browser.

2. Install one host integration

Claude Code

/plugin marketplace add https://github.com/h3tech-ai/marketplace
/plugin install synaptory@h3tech-ai

Reload Claude Code, then run /synaptory doctor.

Codex

codex plugin marketplace add https://github.com/h3tech-ai/marketplace
codex plugin add synaptory@synaptory-dev

Start a new task and invoke $synaptory. Review the first bootstrap dry-run, approve it, and start another new task so Codex discovers the nine managed profiles.

Cursor IDE

Install synaptory from your organization's Cursor Team marketplace, then run:

synaptory skills sync --host cursor

Reload the window and run /synaptory doctor. Cursor headless users must also run the project MCP preflight described in the standalone guide.

3. Configure SPQ explicitly

Create or review .synaptory.yaml at the repository root:

project_id: "my-project"
build_mode: "spq"
engagement_mode: "structured"

tracker:
  backend: "local"
Use an explicit build mode. The compatibility default for an omitted build_mode is still Scrum. Scrum and Kanban are legacy paths planned for retirement.

4. Start the first Cycle

Give Synaptory an outcome and ask it to show the proposed baseline before the first human approval:

Use SPQ to deliver account sign-in with audit logging.
Start Discovery and show me the baseline before Commit.

The lifecycle pauses for baseline approval, approved Cycle scope, Sync entry and clearance, Checkpoint decisions, and final Acceptance. Agents may prepare those decisions but cannot approve for you.

5. Add runtime federation only if needed

synaptory runtimes list
synaptory runtimes doctor

Multiple installed hosts do not automatically collaborate. Cross-runtime execution is SPQ-only and limited to certified profiles and authority ceilings.

Operator preview. The commands above work today. Normal host dispatch does not route through them yet, so setting a runtimes: policy does not change an ordinary Cycle. Follow Epic #339 for the wiring.

Continue reading