Docs / OpenClaw

OpenClaw

OpenClaw is a personal AI assistant you can talk to on Telegram or WhatsApp. Saka installs it on your server with secure defaults, then gives you a management page with no terminal needed.

Install

Open your server in the panel, press + Pasang aplikasi (Install app), then choose OpenClaw. The fields you fill in:

FieldDetails
AI providerAnthropic (Claude), OpenAI, Google Gemini, OpenRouter, or an OpenAI-compatible endpoint (for example 9Router, LiteLLM, vLLM).
Endpoint address and model nameOnly for OpenAI-compatible endpoints. A gateway running on the same server (e.g. 9Router) can be written as http://localhost:20128/v1; Saka points it at the server itself, not inside the container. The gateway must listen on 0.0.0.0; the port stays closed to the internet when the Saka firewall is on.
AI API keyChecked with the provider before installation, then stored only on your server, in a file readable only by root. Token costs are paid directly to your AI provider.
Telegram bot token (optional)From @BotFather, command /newbot. You can leave it empty and add it later. This bot belongs to your assistant, not to Saka.
Using Google Gemini?

Create an API key at aistudio.google.com/apikey and copy it in full (it starts with AIza). The key is checked directly with Google before installation. A Google Workspace subscription or a Gemini subscription (the Gemini app) is not an API key and cannot be used; only an API key from Google AI Studio works.

Server requirements: 2 GB of RAM and 8 GB of free disk. Docker is installed automatically if it is not there yet. Installation takes a few minutes. You can close the dialog; the install keeps running and the result is sent to your Telegram.

The setup Saka installs:

Hermes Agent

The catalog also includes Hermes Agent from Nous Research, an AI assistant that learns from use and talks to you on Telegram. It is installed from the official nousresearch/hermes-agent:latest image and needs 1 GB of RAM and 4 GB of free disk. Its AI providers are the same as OpenClaw's: Anthropic, OpenAI, Google Gemini, OpenRouter, or an OpenAI-compatible endpoint. Hermes replies directly to the Telegram users whose IDs you enter during installation (ask @userinfobot; separate several with commas). Already installed Hermes yourself (Docker or directly)? Saka detects it on the server page and refuses to install a second one. Manage with Saka stops the old Hermes without deleting it, copies its memory, skills, sessions, bot, and keys, and restores it automatically if anything fails. Skipped the Telegram bot during installation? Add it later on the app's Telegram card without reinstalling; data is kept and Hermes restarts in about a minute. Hermes has a management page too: who can chat (people who message the bot create an access request you approve in the panel, or add a Telegram ID directly), change the AI provider, model, or key (the key is checked first), version & updates with an automatic backup before each update, and backups. The full management page below is only for OpenClaw.

Chat access & approval

A new person who messages your bot is not served right away. They receive an access code (pairing), and their messages are not processed until you approve them.

  1. Send any message to your bot on Telegram.
  2. The request appears on the management page within a few seconds, with the sender's name. Match the code with the one from the bot.
  3. Press Setujui (Approve) only if you know the sender.

The list "Yang bisa mengobrol dengan asisten ini" (Who can chat with this assistant) shows everyone who has been approved. Access can be revoked at any time. The owner cannot be revoked from the panel, so you never lock yourself out of your own assistant.

AI models

Channels: Telegram and WhatsApp

Telegram

Enter the bot token during installation, or add it later on the Telegram card. Then use the access approval flow.

WhatsApp

  1. Press Tambah WhatsApp (Add WhatsApp). The first time, Saka downloads the WhatsApp plugin and restarts OpenClaw (±2-3 minutes; the Telegram bot pauses briefly).
  2. A QR code appears in the panel. Scan it from WhatsApp on your phone, just like WhatsApp Web. The QR code refreshes automatically when it expires.
  3. New senders get an access code; approve them on the access card.
WhatsApp risk

OpenClaw connects to WhatsApp as a linked device (like WhatsApp Web), which is an unofficial route. Meta may restrict or block the number used. Use a separate number, not your main number, and do not use it for bulk or promotional messages.

WhatsApp can be disconnected from the panel and reconnected at any time by scanning the QR code. Discord and Slack are coming later.

Schedules & reminders

Create scheduled tasks for the assistant: once (a specific date and time), daily, weekdays, or weekly (pick the days), with times in WIB (UTC+7). Write what the assistant should do, then choose where the result is sent on Telegram or WhatsApp. Schedules can be turned on or off, run now, or deleted.

You can also create schedules through chat, for example "remind me to take my medicine every day at 8 pm".

Web search

Web search is active from installation, with no extra key. You can switch the provider in the panel: parallel-free (default) or DuckDuckGo, or turn it off. Switching providers for the first time downloads a plugin and restarts OpenClaw.

Skills, persona, memory

Dashboard through a tunnel

The Buka dasbor (Open dashboard) button opens OpenClaw's built-in dashboard on a dedicated subdomain <id>-<aplikasi>-dashboard.saka.work, without opening a port on your server:

Default security

SettingSaka defaultWhat it means
Ask before running commandsOnBefore running a command on the server, the assistant sends ✅/❌ buttons to your Telegram. No answer means denied.
Skills from the internet (ClawHub)OffThe assistant cannot download unreviewed third-party skills. Built-in skills can still be used.

Both can be changed on the Keamanan (Security) card, but we recommend keeping the defaults.

Security check: a button on the same card runs OpenClaw's own security audit (±1-3 minutes) and shows the findings with their severity and suggested fixes. This check needs swap so the assistant does not stall; if there is none yet, fix it first from the Readiness card.

Move to another server

Found a cheaper or faster VPS? Install Saka on the new VPS, then on the old server's page press Move to another server on OpenClaw or Hermes. This works for installs managed by Saka and for ones you set up yourself before Saka (Docker or the official installer; Saka detects them automatically). Memory, sessions, settings, AI keys, channel credentials, and the workspace move along; data goes directly between the servers (one-time certificate, only the new server's IP allowed), not through Saka Panel.

  1. The new server is checked and prepared first (RAM, disk, Docker, image) while the old bot keeps running.
  2. The old bot is paused, its data packed, sent, and verified (SHA-256). In our test the pause was about 30 seconds for 18 MB of data; longer when memory or sessions are large. The bot never runs twice, because two bots with the same Telegram token fight over messages.
  3. The bot starts on the new server as a Saka-managed app and is checked to be healthy. The old gateway token is reused, so paired devices stay connected.
  4. If any step fails (for example the new server cannot reach the old one), the old bot is started again automatically. When it succeeds, the old bot is stopped (and does not start again on reboot) but its data is not deleted; remove the old server once you are sure.

AI agents use the MCP tool aplikasi_pindah. Other ways to move (cPanel, Dokploy, Coolify) are in Moving to Saka.

OpenClaw you installed yourself

An OpenClaw installed directly on the server (not Docker, not through Saka) is still recognised in the Other apps card: you can see logs and start, stop, and restart its service from the panel. Saka does not change the service or its data. If OpenClaw is installed as a service but does not start automatically when the server boots, the Readiness card shows a warning and an Enable at boot button, so the bot does not stay down after a reboot.

Backups & updates

If the app is removed, its container is stopped and its data is moved to /var/lib/sakapanel/aplikasi/.sampah/ on the server, where it can be restored manually.