Syncropel Documentation

Learn how to coordinate work between humans and AI agents with immutable records, evidence-based trust, and self-improving workflows.

Run an instance

Pick a path

Sign up at syncropel.com/signup. About 60 seconds. Your instance comes up at <label>.syncropel.app with a bootstrap token shown once.

No install, no machine to maintain. Free tier; paid tiers for scale. Same binary, same APIs, same record store as self-hosted — move between hosted and self-hosted at any time.

Sign up Walkthrough →Pricing

Use it from anywhere

One task across three surfaces

A task becomes a thread of records — INTEND → DO → KNOW. Trust evidence accumulates as work is reviewed.

terminal

$ spl task add "Fix checkout timeout" --alias TASK-0042 --domain code

◇ Task created: Fix checkout timeout · TASK-0042

$ spl task start TASK-0042

$ spl task done TASK-0042 --summary "Pool 10 → 50"

$ SPL_ACTOR=did:sync:agent:director spl task approve TASK-0042

✓ approved · trust(code) 0.473 → 0.501

CLI reference →Task management

Same records, same threads, three surfaces. Add an MCP-compatible AI client (Claude Desktop, Cursor, Cline, Zed, OpenCode) and your assistant sees the same threads.

Start here

Get an instance running on your terms

QuickstartFive minutes from zero to a working loop Hosted signup60-second flow at syncropel.com/signup Install splLinux, macOS, Windows — single binary First runspl init, identity, ~/.syncro/ layout Pair a deviceBrowser, phone, or second CLI on the same instance PricingFree tier + paid tiers — full cost surface

Tutorials

Learn by doing — 15-30 minutes each

Your first taskCreate, complete, and see trust grow Working with threadsOpen, fork, and close workflows Build a workspaceScaffold, edit, test, publish, share

Mental model

What Syncropel actually is, under the hood

RecordsThe 8-field immutable, content-addressed unit ThreadsCoordinated workflows that fold to state ActorsIdentity, trust profiles, persistent memory TrustWilson-LB evidence with the dial PatternsRepeated success captured — replay or adapt at choice

Build with Syncropel

SDKs, AI clients, gateways, dev tools

Task managementFull lifecycle from creation to approval SearchSemantic + full-text across threads NamespacesMulti-tenant scoping with the 5-level hierarchy Debuggingdoctor → status → debug replay → audit export TypeScript SDKUniversal JS/TS — Node, Deno, Bun, Workers Python SDKhttpx-based, fail-open record client body.kind manifestRecord kind grammar and reserved scopes AI clients (MCP)Claude Desktop, Cursor, Cline, Zed, OpenCode api.syncropic.comSingle AI-gateway endpoint, many providers

Operate in production

Day-2 ops, security, recovery

Operator runbookLifecycle, recovery, backup discipline, upgrades spl doctorTop-down diagnostic — start here when stuck Security modelAuth, service accounts, on-disk, threat surface Backup & recoveryProtect data, restore safely TroubleshootingDiagnostic tree for the common failure modes Reset & uninstallClean reset and full uninstall per platform

Reference

Look things up

CLIEvery spl command with flags + examples HTTP APIAll endpoints with request examples Configurationconfig.toml settings, rules, data locations GlossaryKey terms A to Z FAQVocabulary, hosted vs self-hosted, federation

Open source & community

Participate, contribute, file bugs

GitHubSource, releases, the project home DiscussionsQuestions, ideas, show-and-tell IssuesBug reports and feature requests ContributingHow to engage with the project

Browse the full docs hub