The catalogue
OpenClaw
The personal assistant reached from Telegram, Discord or WhatsApp, its gateway as a systemd service, the model providers you configure.
- Module
- ai.openclaw
- Category
- AI agents
What it installs
- OpenClaw through mise on the machine’s Node — 24.16 or later, which the install checks before spending a minute on it — on the path of every shell.
- The model providers you give, as the variables the gateway reads (ANTHROPIC_API_KEY, OPENAI_API_KEY…) in a file only dev can read, and the gateway as a systemd service on 127.0.0.1:18789 when always on.
- The Pupitre skills in ~/.openclaw/skills and ~/.agents/skills, both of which OpenClaw reads. No machine context file: OpenClaw writes its own AGENTS.md in the workspace it bootstraps.
What it asks you for
- One line per provider, as name:key, and whether the gateway stays up between two sessions.
Good to know
The channels — Telegram, Discord, WhatsApp — are wired with openclaw onboard in a terminal on the server: the wizard asks for the bot tokens and writes ~/.openclaw/openclaw.json, which the module never touches. Node 24, the default of the Node.js module, is what it needs: a machine set to Node 22 or 20 has to move to 24 first, and the install says so before doing anything. Uninstalling takes back the CLI, the providers and the service; the workspace, the sessions and the channels stay under ~/.openclaw.