Skip to main content
SCSyndicate Code
Get Started

Using Syndicate Code

Everything you need to work with Syndicate Code day-to-day: the TUI, CLI, sessions, workflows, checkpoints, and specialists.

The TUI

The primary interface is a five-pane terminal UI launched by running syndicate with no arguments. It renders governance state pushed from the control plane and surfaces pending checkpoint decisions for operator review.

The TUI has no authority — it is a read and intent surface. Policy enforcement happens at the control plane, not the UI.

The CLI

syndicate is also a CLI for session management, policy operations, audit queries, and headless workflow execution:

syndicate run --no-tui --objective "summarize dependency drift" --output json
syndicate audit verify
syndicate policy show

See CLI for the full command surface, or CLI Reference for exhaustive flag and exit-code documentation.

Sessions, workflows, and checkpoints

Every interaction is scoped to a session. Within a session, the model submits proposals that traverse the governed execution lifecycle. When policy requires operator input, a checkpoint is surfaced in the TUI.

The operator responds (y to approve, n to deny, d for detail) — the TUI forwards the decision to the control plane, which records the approval, issues a permit, and resumes execution.

In this section

  • TUI — five-pane layout, keyboard bindings, authority model
  • CLI — command surface, flags, headless usage
  • Sessions — session lifecycle, attach, inspect, export
  • Workflows — workflow entry point, autonomy modes, dry run
  • Checkpoints — checkpoint types, presentation, invariants
  • Specialists — registering and managing specialist agents