Documentation

Deploy a VM, connect an agent, and start working.

Get started

  1. Create your free account.
  2. Choose shared hosting or a private VM, its size, and an agent.
  3. Review the monthly price and pay. Your VM starts after payment.
  4. Open the agent and connect its model access. Messaging is optional.

Your account is free. VMs are paid monthly in advance; model usage is separate.

Choose your agent

AgentWorkspaceMessaging
Claude CodeCoding terminal and browserTelegram
Codex CLIBeta · selected accountsCoding terminal and browserTerminal only
HermesBeta · selected accountsTerminal with browser toolsTerminal only
OpenClawChat, control panel and browserTelegram, WhatsApp, Discord, Slack
OpenCodeBeta · selected accountsCoding terminal and browserTerminal only

Setup shows what is available for your account and VM. Private managed agents need Medium or larger. Small private VMs support your own software over SSH. OpenClaw and Hermes use shared hosting.

VMs & agents

  • VMs: each card is one VM or existing shared workspace. Open its agent, or use Manage VM for resources, power, SSH and billing.
  • Agents: switch between terminals and chats in one workspace. Each agent has its own settings and messaging connections.
  • Overview: view your VMs and their installed agents. Lines show actual hosting relationships.

Workspace

Choose an agent in the left sidebar. Use its view menu for Terminal or Chat, Browser, or Split. Hermes has no Browser or Split view; use its browser tools from the terminal.

  • Choose a layout for up to 12 panes. Drag pane headers to rearrange them and drag dividers to resize.
  • Collapse the sidebar to icons or hide it from its display menu. The top-left button brings it back.
  • Save named layouts to return to the same arrangement.
  • Use the pane’s options menu for Agent settings, Usage & status, and the classic view.
  • In Browser view, choose Control to send input and Release when finished. Fullscreen gives the browser more room.

Closing a pane leaves the agent running. On mobile, use the navigator button to switch agents.

Model access

  • Claude Code: sign in with your Claude account or Anthropic credentials in the terminal.
  • Codex CLI: connect ChatGPT or your OpenAI API key in the terminal.
  • OpenCode: use /connect and /models for your provider or available OpenCode models.
  • OpenClaw and Hermes: new shared VMs use separately purchased model credits. Existing agents keep their original model access.
  • Megaloop: save a key in Settings → Model connections. On supported VMs, choose it during agent installation or under Agent settings → Model access. Claude Code and Codex CLI are supported. Megaloop bills that usage; pwrd credits are not used. pwrd currently cannot switch a connected agent back to provider sign-in or credits.

Connect the model access required by your chosen agent before sending a task. pwrd does not include a Claude or ChatGPT subscription with a VM.

Messaging

Open Agent settings to connect a supported channel.

Telegram · OpenClaw and Claude Code

Choose Quick setup for a supplied bot, or create a bot with @BotFather using /newbot and paste its token.

For Claude Code, sign in first, message the bot, then run /telegram:access pair <code> in its terminal. OpenClaw messaging permissions are managed in Agent settings.

WhatsApp · OpenClaw

Choose a personal or dedicated number, then show the QR code. In WhatsApp, open Settings → Linked Devices → Link a Device and scan it.

Discord · OpenClaw

Create an application in the Discord Developer Portal. Enable Message Content Intent and Server Members Intent, invite the bot to your server, and paste its bot token. The connection dialog includes the required steps.

Slack · OpenClaw

Create a Slack app, enable Socket Mode, and install it in your workspace. Connect it with the app token (xapp-…) and bot token (xoxb-…).

OpenClaw permissions: choose who can send direct messages and whether groups require a mention. Allowing every group message increases usage. Telegram may require BotFather’s /setprivacy setting for this mode.

Billing & files

  • Each VM has its own monthly subscription. Stopping it preserves its disk and continues billing.
  • Cancel renewal to keep the VM until its paid-through date. The VM and its files are deleted after that date; export anything you need first.
  • Delete a private VM’s agents before destroying it. Destroy removes the VM and stops renewal; unused prepaid time is not refunded.
  • Deleting an agent on a private VM leaves that VM and its subscription in place. Deleting a shared-hosting agent destroys that hosting and cancels its subscription.
  • Model credits are shared across your account. When the available balance cannot cover a request, model requests stop and the VM remains available.
  • Existing account subscriptions and included workspaces are preserved and billed separately.

Help

  • VM still building: leave setup open. It updates automatically when the VM is ready.
  • Agent not responding: check Usage & status, model sign-in, and available credits. Restart agent restarts its software; restarting a private VM interrupts every agent and application on it.
  • SSH: use the command in VM → Access and the key selected at purchase. Public applications use tunnels; private VMs expose SSH only.
  • Connection trouble: retry the connection or contact support.
For VM sizes and monthly prices, see Pricing.