Skip to content
Dispatch

Trust and data boundaries

Dispatch runs locally, and evaluation sync is opt-in.

Dispatch stores snapshots, evidence, and evaluations on your machine. Nothing is sent to Dispatch Cloud until you enable sync and run the sync command.

Local execution

Dispatch runs on your machine and stores its run evidence locally. A Cloud account is not required.

Sync off by default

Recording a local evaluation does not enable sync or send the evaluation.

Payload preview

You can inspect the exact evaluation payload before choosing whether to sync it.

Upload requirements

Upload requires consent, a server-issued preview token, and a separate sync command.

Current sync boundary

Review the Cloud sync payload.

Optional sync can send eligible evaluation data. Source code and local run evidence stay on your machine.

Excluded from Cloud sync

These stay outside the current Dispatch Cloud evaluation payload.

  • Source snapshots and patches
  • Execution logs and exact agent prompts
  • Local paths, credentials, and environment data
  • Changed filenames and project-check command text

Eligible after opt-in

These fields may appear in the evaluation payload you preview.

  • Exact task text
  • Runtime and environment metadata
  • Agent and model identity
  • Usage and diff counts
  • Configured check results
  • Your choice and why you made it

Explicit sync flow

Use separate commands to preview, enable, and upload.

Enabling sync records consent and queues eligible data locally. Dispatch uploads it only after you run a separate sync command with a configured token.

Optional Cloud sync
dispatch sync preview <run-id>
dispatch sync enable
dispatch sync

  1. 01

    Inspect

    See the exact body before consent.

  2. 02

    Enable

    Consent and queue locally.

  3. 03

    Sync

    Upload only with a valid token.

Third-party boundary

Your agent providers’ terms still apply.

Dispatch Cloud and agent providers

Dispatch Cloud receives no source code. Codex CLI, Cursor Agent, and other agent tools may communicate with their own providers, whose settings, policies, and data controls apply.

What the unsafe-local flag means

The flag confirms that local agents can change files and run commands. There is no security sandbox, so start with a repository you can restore.

Preview limitations

Current v0.1 limits.

No automatic winner or automatic routing
No hosted execution
No polished cloud dashboard
No billing or team system
Docker support is experimental, without turnkey images for real agent tools

Run your first local comparison.

Follow the quick start with a restorable repository. Cloud sync stays off unless you choose to enable it.

Read getting started