CLI quickstart
Your first half hour as a platform developer: build the tide CLI, bring up the local dev stack, sign in to GitHub, and run a first coding session that changes nothing.
Check the CLI
tide --helpConfig resolves from ./tide.yaml or ~/.tide.yaml, then TIDE_* environment variables, then flags (see CLI reference).
Run the apps locally
tide dev up runs the apps natively (no VMs, no images, no sudo in the run loop): both app backends, the shared inference server (mistralrs-server), the Flutter UIs, and the security stack (envelope encryption, pipe mesh, rotating raft mTLS, eBPF).
tide dev up # everything (the default is all)
tide dev up face # one app
tide dev down # stop everythingThings tide dev up needs:
- The app checkouts. It reads the environment variables
FACE_REPOandPULSE_REPO(defaults../faceand../pulse), not the CLI’s--face-repoflag. - A
mistralrs-serverbinary and GGUF weights. Without them it logsmistralrs-server binary or model not found under … — apps spawn their own if configured.and carries on. - Flutter, for the console UI. Without it you see
console skipped (flutter not found).
Run state goes under .dev/: logs are .dev/*-{backend,frontend}.log, PIDs are .dev/<name>.pid, and ports are written to .dev/ports.env. On first run it mints a dev mesh CA and generates a per-machine envelope KEK at .dev/secrets/TIDE_ENVELOPE_KEK with crypto/rand (delete that file to rotate it).
Get portless URLs (one-time sudo)
tide dev hosts # map *.runink.org.local → 127.0.0.1 and grant the gateway :443
tide dev secure # optional: add the single mTLS SNI gatewayThe success banner ends with TIDE dev up (envelope + pipe-mesh + rotating raft mTLS + eBPF + diagnostics/MCP + self-heal). followed by the per-app URLs. The TIDE console runs as a shell only (/api/* needs the operator and a cluster).
Sign in to GitHub
tide auth login # GitHub Device Flow, cached in ~/.core/auth.json
tide auth statustide session uses this token by default. It switches to GitHub App installation tokens only when TIDE_GH_APP_ID and TIDE_GH_APP_PRIVATE_KEY (or TIDE_GH_APP_PRIVATE_KEY_FILE) are set, which is meant for unattended runs.
Run a first coding session, safely
tide session start --repo <owner>/<repo> \
--prompt "Summarise the README, then call done" \
--dry-run--dry-run runs the full loop but never pushes or opens a PR; it prints the diff instead. With no --inference-url, the CLI probes local endpoints and logs using inference endpoint … (auto-discovered). Every run_shell and browser_* call stops at a [y/N] prompt. See Coding Sessions.
Where the DevEx pages are
In the console, open the DevEx group in the rail. Each page can be deep-linked as ?tab=<name> (for example ?tab=gitops). The DevEx rows are described on the DevEx page, and the whole rail is mapped in the console map.
Deploying to a cluster instead
tide dev is the local run loop. Deploying to k0s is a different layer: tide deploy platform|face|pulse|all with --mode local (multipass VMs) or --mode onhost (a single-node k0s on the host itself). See CLI reference.