OpenClaw, ready out of the box. Paste a command and let the bot work.

Telegram is fast to set up, stable for long-running bots, and familiar to most users. It gives you a simple path to go live first, then expand to more channels later.

Bot Token is your bot's secret key from @BotFather. User ID is the numeric ID of who is allowed to chat with your bot - in most cases that's your own Telegram User ID (find it via @Getmyid_bot or @userinfobot). Token identifies the bot; User ID controls access.

Relaunch means starting your bot on a fresh server with your latest settings. Use it when a server has issues, disk is full, you want a new bot token, or you want a clean restart. You get up to 10 free relaunches every 30 days, with optional encrypted memory restore.

Go to Profile > Overview, find the agent card, and click the Hermes / OpenClaw switch. If the switch is disabled on an existing deployment, relaunch that deployment first: Profile > Overview > deployment card > Settings > Relaunch. Relaunch keeps chat history and memory by default.

If you want the fastest OpenClaw or Hermes Agent setup and less ops work, cloud is usually better: installation is automated, uptime is easier, and relaunch/recovery is built in. Mac mini is great when you want full local control and already manage your own hardware. In practice, many users start in cloud and move parts in-house later.

If you are unsure, start with the default model that ClawSimple preselects for your plan. It is chosen for balanced quality, speed, and cost. You can switch models anytime later.

Our billing is transparent and real-time: if you connect your own AI account, we charge for setup and operations. If you use the built-in AI quota, you are charged based on actual OpenRouter model usage costs (we automatically choose the most cost-effective provider); on top of that, we add only a 15% forwarding service fee.

Not as a separate server subscription. An extra agent reuses the same deployment and server, so you are not buying another server just to add one more bot. What does grow is usage: more agent traffic can consume the deployment's managed AI credits faster, or increase usage on your own AI account if that server uses your own provider.

At minimum, a fresh Telegram Bot Token for that new bot and the AI choice for that agent. The allowlist usually defaults to your saved Telegram User ID, but you can change it. If the agent uses your own AI account, the server-level provider connection must already exist and the agent still needs a model selection.

Go to Profile > Overview, open the deployment card, click Add Agent, fill in the bot token and model settings, then submit. ClawSimple queues an add_agent job, updates the running OpenClaw config on that same deployment, and the new bot appears as active once the job finishes.

There is no single fixed number in the current product logic. A few light Telegram assistants on one deployment are usually fine; pressure shows up when several agents are all active at once, especially if they run long tool calls or heavier models. Managed AI credits are tracked at the deployment or seat level, so agents on the same deployment share that usage bucket.