Quick Start

Go from zero to a running AI agent in 2 steps.

Prerequisites

• Node.js 18 or later
• npm (included with Node.js)
• A LaunchPod account (sign up free)

Step 1: Install the CLI

Install the LaunchPod CLI globally using npm:

Verify the installation:

Step 2: Launch

One command handles everything — sign-in, framework and tier selection, provisioning, and connection. If you're not logged in, a browser window opens automatically.

You now have a full bash shell on your VM. You can check status at any time from a separate terminal:

Step 3: Onboard Your Agent

The openclaw onboard wizard starts automatically once you connect. It walks you through choosing an AI provider (bring your own key) and a messaging channel.

Finally, pair your messaging app from the terminal:

That's it. Your AI agent is live and running 24/7 on a dedicated cloud VM. No Docker, no containers — just a native Node.js environment you fully control.

Managing Your Instance

Once your instance is running, use these commands to manage it from any terminal.

Reconnect to your instance

If you close your terminal or get disconnected, reconnect at any time:

Terminal access is available when your instance status is awaiting_setup or running.

Check instance status

View detailed information about your instance including resource usage:

List all instances

See all your instances and their current status:

View logs

Check your instance logs to debug issues or monitor activity:

Exit the terminal

To disconnect from your instance terminal, type exit or press Ctrl+D. Your instance keeps running in the background — disconnecting does not stop it.

Pod Tiers

Each instance runs on a dedicated Hetzner Cloud VM in Ashburn, VA. Choose the tier that fits your workload:

All tiers include:

• Dedicated VM (not shared or containerized)
• Native Node.js 22 environment
• Secure Cloudflare tunnel (no open ports)
• SSH terminal access via launchpod connect
• Ubuntu 24.04 LTS

Billing & Upgrades

Manage your subscription, upgrade, or downgrade your plan through the Stripe billing portal:

From the billing portal you can:

• View your current plan and billing history
• Upgrade or downgrade your tier
• Update your payment method
• Cancel your subscription

Plan changes take effect at the start of your next billing cycle. If you cancel, your instance remains active until the end of the current period.

Troubleshooting

Common issues and how to fix them.

Terminal connection keeps dropping

Symptoms: After running launchpod init or launchpod connect, the terminal connection closes unexpectedly.

Solutions:

• Check your internet connection — the terminal requires a stable WebSocket connection.
• Wait for SSH to be ready — if the instance just provisioned, SSH may not be fully initialized. The CLI retries automatically for up to 25 seconds.
• Reconnect manually:
  $ launchpod connect openclaw-1234567890
• Check instance status:
  $ launchpod status openclaw-1234567890
  Terminal is only available when status is awaiting_setup or running.

Cannot connect to instance

Error: Terminal connection failed: Connection closed (code 1011)

Solutions:

• Verify the instance is running: launchpod status <name>
• If status is failed, cancel your subscription and create a new instance:
  $ launchpod billing $ launchpod init
• Check for firewall or VPN issues blocking WebSocket connections

Login fails or times out

Symptoms: launchpod login opens browser but never completes.

Solutions:

• Make sure you complete the sign-in flow in the browser window
• Check that popups aren't blocked for api.launchpod.dev
• Try logging in again — the CLI polls for 2 minutes:
  $ launchpod login

Commands fail with "Unauthorized"

Error: Failed to authenticate. Please run: launchpod login

Solution: Your session may have expired (tokens last 30 days). Log in again:

Instance stuck in "provisioning"

Symptoms: launchpod init shows "Provisioning..." for more than 5 minutes.

Solutions:

• Check status in another terminal window:
  $ launchpod list
• If stuck for more than 10 minutes, contact support at hello@santuri.com with the instance name
• As a last resort, cancel via launchpod billing and recreate the instance

Provisioning failed

Error: Instance provisioning failed

Solutions:

• Check your subscription is active: launchpod billing
• You can have up to 1 instance at a time. Check if you already have one: launchpod list
• Cancel and recreate:
  $ launchpod billing $ launchpod init

Cannot create instance — no subscription

Error: No active subscription found

Solution: Subscribe to a plan:

This opens Stripe checkout where you can select a tier and subscribe.

Subscription is active but cannot create instance

Symptoms: Paid for subscription but still getting "no subscription" error.

Solutions:

• Wait 1–2 minutes for webhook processing to complete
• Log out and back in to refresh your session:
  $ launchpod logout $ launchpod login
• If still failing after 5 minutes, contact support at hello@santuri.com

Terminal shows blank screen

Symptoms: Connected successfully but terminal shows no output.

Solutions:

• Press Enter to trigger a prompt
• Try resizing your terminal window (triggers a refresh)
• Disconnect and reconnect:
  $ launchpod connect <name>

Cannot exit terminal

Symptoms: Terminal is stuck and Ctrl+C doesn't work.

Solution: Use Ctrl+D or type exit to close the SSH session. If completely frozen, close the terminal window. Your instance continues running.

Still need help?

If your issue isn't covered here, email us at hello@santuri.com.

CLI Reference

All available commands in the LaunchPod CLI: