GeezerVison

Command-line interface for the Strait orchestration platform

Website · Documentation · Platform repo · Releases

Strait is an open-source job orchestration platform. Your code stays on your infrastructure — Vercel, Cloudflare Workers, AWS Lambda, Netlify, Express, Kubernetes, or a long-lived Go worker. Strait schedules, retries, fans out, and observes — it does not host your code.

Two transports, one mental model:

• strait.serve — Strait calls a signed HTTPS endpoint you expose (push).
• strait.worker — your process holds a long-lived gRPC stream and pulls tasks (pull).

This repo ships the CLI: scaffold projects, register jobs, manage endpoints, run a local tunnel, inspect runs, and operate workers.

# Homebrew (macOS / Linux)
brew install strait-dev/tap/strait

# From source (requires Go 1.26+)
go install github.com/strait-dev/cli/cmd/strait@latest

Pre-built binaries for darwin/linux/windows on GitHub Releases.

# 1. Scaffold a starter project (pick any template — see `strait init --list`)
strait init --template vercel --name my-app

# 2. Authenticate with the orchestrator (opens a browser)
strait auth login

# 3. Sync strait.json orchestration definitions
cd my-app && strait sync

# 4. Point Strait at your deployed endpoint and round-trip a signed canary
strait endpoint set hello https://my-app.vercel.app/api/strait
strait endpoint verify hello

# 5. Watch a run end-to-end
strait runs watch <run-id>

Workers are SDK programs, not CLI processes — scaffold one and run it on your own infrastructure:

strait init --template go-worker --name my-worker
cd my-worker && go run .          # opens a gRPC stream to the orchestrator
strait worker status              # confirm it's connected

strait dev launches a Cloudflare Quick Tunnel, rewrites each job's endpoint_url to point at the tunnel, and restores the original URLs on exit. Drop into any scaffold:

strait dev

strait init --template <name> scaffolds a working starter. Currently:

Each scaffold ships a starter strait.json so strait sync works immediately.

Example strait.json:

{
  "$schema": "https://schemas.strait.dev/v1/strait.json",
  "version": "1",
  "jobs": [
    {
      "slug": "hello",
      "name": "Hello",
      "endpoint_url": "https://my-app.example.com/api/strait",
      "max_attempts": 3,
      "timeout_secs": 30
    }
  ],
  "workflows": []
}

strait --help shows the full tree. Canonical groups:

strait deploy push is deprecated and currently delegates to strait sync for compatibility. New scripts should use strait sync.

Strait CLI reads configuration from (in order of precedence):

1. Command-line flags (--server, --project, --org, --api-key)
2. Environment variables (STRAIT_SERVER, STRAIT_PROJECT, STRAIT_ORG, STRAIT_API_KEY)
3. Per-project file: ./.strait.yaml
4. User-global file: ~/.config/strait/config.yaml

Org-scoped commands (billing, some usage views) resolve the organization from --org, then STRAIT_ORG, then the org config key or active context.

Credentials from strait auth login are stored in the OS keychain (macOS Keychain, Linux Secret Service, Windows Credential Manager).

Every command supports --format json|yaml|csv|table|jsonpath|go-template for machine output and --quiet to suppress styling.

make build         # build binary to bin/strait
make test          # run tests with race detector
make lint          # golangci-lint
make check         # vet + lint + test
make hooks         # install lefthook pre-commit hooks
make mutation-dry  # run Gremlins coverage analysis without mutating code
make mutation      # run Gremlins mutation testing → bin/gremlins-report.json
make refresh-openapi  # vendor the server OpenAPI spec into internal/client/testdata
make e2e           # live end-to-end suite (needs STRAIT_SERVER/STRAIT_API_KEY/STRAIT_PROJECT)

Mutation testing is pinned to go-gremlins/gremlins v0.6.0 via go run, so no separate install step is needed. Scope local runs with MUTATION_ARGS, e.g. make mutation MUTATION_ARGS="--diff origin/main".

The CLI's request paths are validated against the server's OpenAPI spec (vendored at internal/client/testdata/openapi.json). TestEndpointsMatchOpenAPISpec in internal/client statically extracts every endpoint the client calls and fails the build if any path is missing from the spec — so CLI/server drift is caught in CI. After a server API change, run make refresh-openapi (against a running server) to update the vendored spec.

See AGENTS.md for the contributor operating guide.

Email [email protected] — see SECURITY.md.

MIT