The fastest path is the install script. It detects your OS + arch, fetches the matching signed bundle from download.flocks.sh, verifies the SHA-256, and drops the CLI in ~/.local/bin. 
curl -sSfL https://flocks.sh/install.sh | sh

​
Bring up a gateway

flocks dev --bind 127.0.0.1:7700
dev runs gateway + coordinator + roost in a single process with process-class isolation. Perfect for development; not the trust posture you’d ship to a fleet (see modes).

​
Talk to it

curl -sf http://127.0.0.1:7700/healthz | jq .
# { "status": "ok", "node_id": "ed25519:…" }

​
Run an agent through it

curl -sf http://127.0.0.1:7700/v1/execute \
  -H 'Content-Type: application/json' \
  -d '{
    "idempotency_key": "demo-1",
    "task": "Respond exactly: flocks-playground-ok",
    "driver": "codex",
    "auth_token": "desktop-gateway"
  }' | jq .
The CLI you ask for has to be on $PATH of the roost. The codex, claude, and gemini drivers shell out to their respective vendor CLIs — Flocks just wraps the lifecycle.

​
What’s next

Concepts

Gateway, roost, driver, grant — the four words that explain everything.

Modes

From dev (one laptop) to platform (Firecracker tenants).

Drivers

Eight in-tree drivers, plus how to write your own.

Connect (desktop)

The macOS/Linux/Windows app for inspecting + driving your mesh.