Skip to main content
Use the workflow map to move from setup to discovery, authoring, shipping, and operations.

Bootstrap

Prepare a machine, account, or automation session.

Discovery

Inspect state before changing it.

Authoring

Create and modify components, tools, and content.

Flat-File Sync

Work on a project as files on disk instead of only through Studio. See Flat-File Sync for the full workflow.

Shipping

Move runtime package pins.

Operating

Configure and maintain a live project.

Resources

Resource commands expose lower-level server objects for scripts and advanced workflows. Common resource families include projects, organizations, assets, folders, collections, tags, saved searches, dependencies, preview links, packages, and types. Prefer the authoring and shipping families when they match the job. Use resource commands when a workflow needs direct access to an underlying object.

Meta

Boundaries

  • Project API keys authenticate MCP hosts, not operator CLI sessions.
  • rollback and upgrade move tool pins; they do not delete package history.
  • doctor is read-only; publishing, rollback, upgrade, and delete workflows change state.
  • Component history and project package history operate at different layers.
  • pull and inspect are read-only; push, install, and mv write local or draft state but never publish.
  • inspect reads a directory only. It needs no project context and makes no network call.