spawn/ovh
A 6c7ced54dd
fix: replace log_warn with log_step/log_info for non-warning messages (#604)
Agent: ux-engineer

Many shell scripts misused log_warn (yellow) for normal progress/status
messages, making routine operations appear alarming. This fixes 59 files:

- Progress messages -> log_step (cyan): "Injecting environment variables...",
  "Attaching volume...", "Powering on instance...", "Retrieving server IP...",
  "Terminating sandbox/server...", "Creating datacenter...", "Importing SSH key...",
  "Deleting service/app...", "Modal not authenticated. Running setup..."
- Informational notices -> log_info (green): WhatsApp QR code authentication
  notices (30 nanoclaw scripts), codespace delete hints (14 scripts),
  "Appending environment variables to ~/.zshrc..." (6 local scripts),
  credential prompt hints, package update skipped, app reuse notices

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-02-12 03:24:30 -08:00
..
lib refactor: replace custom credential/polling logic with shared helpers in kamatera and ovh (#564) 2026-02-11 17:54:23 -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: replace log_warn with log_step/log_info for non-warning messages (#604) 2026-02-12 03:24:30 -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 Cline and gptme on OVHcloud (#126) 2026-02-09 20:18:28 -08:00

OVHcloud

OVHcloud Public Cloud instances via REST API. OVHcloud

Setup

OVHcloud uses signature-based API authentication. You need:

  1. Application Key and Application Secret - Create at https://api.ovh.com/createToken/
  2. Consumer Key - Generated during token creation
  3. Project ID - Find at OVH Manager (select project -> Project ID)

Required API permissions:

  • GET /cloud/project/*
  • POST /cloud/project/*
  • DELETE /cloud/project/*
  • GET /me

Environment Variables

Variable Description
OVH_APPLICATION_KEY OVH Application Key
OVH_APPLICATION_SECRET OVH Application Secret
OVH_CONSUMER_KEY OVH Consumer Key
OVH_PROJECT_ID OVH Public Cloud Project ID
OVH_SERVER_NAME Instance name (optional, prompted if not set)
OVH_FLAVOR Instance flavor (default: d2-2)
OVH_REGION Region (default: GRA7)
OVH_SSH_USER SSH user (default: ubuntu)

Agents

Claude Code

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

Aider

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

OpenClaw

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

NanoClaw

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

Cline

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

Codex CLI

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

Goose

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

Open Interpreter

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

Gemini CLI

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

Amazon Q CLI

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

OpenCode

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

Plandex

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

gptme

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

Non-Interactive Mode

OVH_SERVER_NAME=dev-mk1 \
OVH_APPLICATION_KEY=your-app-key \
OVH_APPLICATION_SECRET=your-app-secret \
OVH_CONSUMER_KEY=your-consumer-key \
OVH_PROJECT_ID=your-project-id \
OPENROUTER_API_KEY=sk-or-v1-xxxxx \
  bash <(curl -fsSL https://openrouter.ai/lab/spawn/ovh/claude.sh)