spawn/northflank
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 fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 2026-02-11 14:37:43 -08:00
aider.sh fix: validate MODEL_ID from environment to prevent command injection (#548) 2026-02-11 15:41:10 -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 gptme agent for Northflank (#242) 2026-02-10 12:54:09 -08:00

Northflank

Northflank container platform via CLI with exec access. Northflank

Uses Northflank CLI for container exec. Free tier: 2 services. Pay-per-second pricing.

Agents

Claude Code

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

OpenClaw

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

Aider

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

NanoClaw

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

Goose

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

Codex CLI

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

Open Interpreter

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

Gemini CLI

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

Amazon Q CLI

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

Cline

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

gptme

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

Setup

  1. Create a Northflank account at https://northflank.com
  2. Generate an API token at https://northflank.com/account/settings/api/tokens
  3. Install the Northflank CLI:
npm install -g @northflank/cli

Non-Interactive Mode

NORTHFLANK_SERVICE_NAME=spawn-dev \
NORTHFLANK_PROJECT_NAME=spawn-project \
NORTHFLANK_TOKEN=your-token \
OPENROUTER_API_KEY=sk-or-v1-xxxxx \
  bash <(curl -fsSL https://openrouter.ai/lab/spawn/northflank/claude.sh)

Environment Variables

Variable Description Default
NORTHFLANK_TOKEN Northflank API token (prompted)
NORTHFLANK_SERVICE_NAME Service name (prompted)
NORTHFLANK_PROJECT_NAME Project name spawn-project
OPENROUTER_API_KEY OpenRouter API key (OAuth or prompted)

Free Tier

Northflank offers a Developer Sandbox with:

  • 2 free services
  • 2 free cron jobs
  • 1 free database/add-on

Perfect for testing and hobby projects. Production apps should use pay-as-you-go pricing.

Pricing

Pay-per-second usage-based pricing after free tier:

  • Compute: $0.01667 per vCPU/hour, $0.00833 per GB memory/hour
  • Disk: $0.30/GB per month
  • Network egress: $0.15/GB