vrr/spawn
2
0
Fork 0
mirror of https://github.com/OpenRouterTeam/spawn.git synced 2026-05-05 15:40:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8
spawn/netcup
History
A 0835b35a36
fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534) 
~1500 progress messages across 481 files were using log_warn (yellow)
for normal status updates like "Installing...", "Setting up...",
"Creating server...", etc. This made users think something was wrong
when everything was proceeding normally.

Changes:
- Replace log_warn with log_step for all progress/status messages
- Keep log_warn only for actual warnings (errors, remediation hints)
- Remove emoji from 3 sprite completion messages

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
2026-02-11 14:37:43 -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: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -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 for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
continue.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
gemini.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
goose.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
gptme.sh fix: use log_step for progress messages in recent scripts (#524) 2026-02-11 14:04:14 -08:00
interpreter.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
nanoclaw.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -08:00
openclaw.sh fix: use log_step for progress messages in netcup scripts (#441) 2026-02-11 04:45:44 -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
README.md feat: Add amazonq support for Netcup (#460) 2026-02-11 07:00:23 -08:00

README.md

Netcup Cloud

Netcup VPS cloud via REST API. Netcup

Agents

Claude Code

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

Aider

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

Goose

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

Amazon Q

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

Non-Interactive Mode

NETCUP_SERVER_NAME=dev-mk1 \
NETCUP_CUSTOMER_NUMBER=12345 \
NETCUP_API_KEY=your-api-key \
NETCUP_API_PASSWORD=your-api-password \
OPENROUTER_API_KEY=sk-or-v1-xxxxx \
  bash <(curl -fsSL https://openrouter.ai/lab/spawn/netcup/claude.sh)

Authentication

Netcup uses session-based REST API authentication with three credentials:

  1. NETCUP_CUSTOMER_NUMBER - Your customer number
  2. NETCUP_API_KEY - API key from SCP
  3. NETCUP_API_PASSWORD - API password from SCP

Get your credentials:

The scripts will:

  1. Check for credentials in environment variables
  2. Check ~/.config/spawn/netcup.json
  3. Prompt for credentials if not found
  4. Save credentials to config file for reuse

Pricing

Budget VPS provider starting at approximately €3.86/month for entry-level VPS plans. Netcup offers flexible pricing with hourly billing or annual contracts.

API

Netcup's REST API launched in October 2025. It uses session-based authentication (login to get session ID, then use session ID for API calls). The API replaces the legacy SOAP web service (discontinued May 1, 2026).

API documentation is available in the Server Control Panel → REST API Docs.