spawn/latitude
A c8d7ea23e6
refactor: simplify BinaryLane wait loop and fix log_warn in 7 cloud polling loops (#538)
Replace 25-line custom _binarylane_wait_for_active with 4-line
generic_wait_for_instance call, matching the pattern used by 7 other
clouds (DigitalOcean, Vultr, Linode, etc).

Change log_warn to log_step for status/progress messages in polling
loops across 7 cloud providers (aws-lightsail, exoscale, fly, kamatera,
latitude, ovh, scaleway). These are normal status updates, not warnings.

Agent: complexity-hunter

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>
2026-02-11 14:59:51 -08:00
..
lib refactor: simplify BinaryLane wait loop and fix log_warn in 7 cloud polling loops (#538) 2026-02-11 14:59:51 -08:00
aider.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
amazonq.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
claude.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
cline.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
codex.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
continue.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
gemini.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
goose.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
gptme.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
interpreter.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
kilocode.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
nanoclaw.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
openclaw.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
opencode.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
plandex.sh fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
README.md feat: Add Latitude.sh cloud provider with all 13 agents (#85) 2026-02-09 08:33:47 -08:00

Latitude.sh

Bare metal and VM cloud servers via REST API. Latitude.sh

Agents

Claude Code

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/claude.sh)

OpenClaw

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/openclaw.sh)

NanoClaw

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/nanoclaw.sh)

Aider

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/aider.sh)

Goose

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/goose.sh)

Codex CLI

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/codex.sh)

Open Interpreter

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/interpreter.sh)

Gemini CLI

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/gemini.sh)

Amazon Q CLI

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/amazonq.sh)

Cline

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/cline.sh)

gptme

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/gptme.sh)

OpenCode

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/opencode.sh)

Plandex

bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/plandex.sh)

Non-Interactive Mode

LATITUDE_SERVER_NAME=dev-mk1 \
LATITUDE_API_KEY=your-api-key \
OPENROUTER_API_KEY=sk-or-v1-xxxxx \
  bash <(curl -fsSL https://openrouter.ai/lab/spawn/latitude/claude.sh)

Environment Variables

Variable Description
LATITUDE_API_KEY Latitude.sh API key (required)
LATITUDE_SERVER_NAME Server hostname (prompted if not set)
LATITUDE_PROJECT_ID Project ID (auto-detected from first project)
LATITUDE_PLAN Server plan (default: vm.tiny)
LATITUDE_SITE Data center site (default: DAL2)
LATITUDE_OS Operating system (default: ubuntu_24_04_x64_lts)
OPENROUTER_API_KEY OpenRouter API key for agent access

Available Plans

Plan Specs Price
vm.tiny 4 vCPUs, 8GB RAM $0.07/hr
vm.small 8 vCPUs, 16GB RAM $0.14/hr
vm.medium 12 vCPUs, 24GB RAM $0.25/hr
m4.metal.small AMD 4244P (6 cores), 64GB RAM $0.37/hr

Available Sites

US (Dallas, LAX, NYC, Chicago, Ashburn, Miami, Silicon Valley), Brazil, Australia, Chile, Japan, Mexico, UK, Germany, Argentina, Colombia, Singapore, Netherlands.

Get your API key at: https://www.latitude.sh/dashboard (Settings & Billing -> API Keys)