openclaw-remote-minimax-setup

Deploy and configure OpenClaw on a remote Linux server over SSH with MiniMax M2.1 (China API) and a Telegram bot. Use when provisioning a fresh VPS, reproducing a working OpenClaw + MiniMax + Telegram setup, or debugging common first-boot failures such as `gateway.mode=local`, Telegram `chat not found`, and systemd user-service persistence after SSH disconnect.

install

source · Clone the upstream repo

git clone https://github.com/win4r/openclaw-remote-minimax-setup-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/win4r/openclaw-remote-minimax-setup-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skill/openclaw-remote-minimax-setup" ~/.claude/skills/win4r-openclaw-remote-minimax-setup-skill-openclaw-remote-minimax-setup && rm -rf "$T"

OpenClaw · Install into ~/.openclaw/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/win4r/openclaw-remote-minimax-setup-skill "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skill/openclaw-remote-minimax-setup" ~/.openclaw/skills/win4r-openclaw-remote-minimax-setup-skill-openclaw-remote-minimax-setup && rm -rf "$T"

manifest: skill/openclaw-remote-minimax-setup/SKILL.md

source content

OpenClaw Remote MiniMax Setup

Set up a remote OpenClaw host in a repeatable, low-surprise way.

Scope

Use this skill for remote Linux deployments where the user provides:

SSH access
A MiniMax API key
A Telegram bot token
A target model of
```
minimax/MiniMax-M2.1
```

Prefer the official OpenClaw documentation first, then execute the deployment over SSH.

Read these references when needed

Read
```
references/workflow.md
```
for the full deployment flow.
Read
```
references/config-template.md
```
before writing or patching the remote OpenClaw config.
Read
```
references/failure-modes.md
```
when Telegram does not reply, the gateway exits after install, or the service dies after SSH disconnect.

Core rules

Do not publish or store user secrets in the skill, repo, or commit history.
Replace all secrets in examples with environment placeholders.
Validate the remote config before declaring success.
Verify both the model path and the Telegram path.
Treat a successful install as incomplete until the service survives SSH disconnect.

Minimal workflow

Read the relevant OpenClaw docs for installation, providers, and Telegram.
Inspect the remote host: OS, sudo availability,
```
curl
```
,
```
node
```
, and
```
openclaw
```
.
Install OpenClaw safely.
- Prefer fetching the official installer locally, reviewing it, copying it to the remote host, and executing it there.
Write a minimal config using the MiniMax China endpoint and Telegram bot token.
Run
```
openclaw config validate
```
.
Ensure
```
gateway.mode=local
```
before first service start.
Install and start the gateway service.
Enable persistence for
```
systemctl --user
```
deployments.
- On remote VPS installs, run
```
sudo loginctl enable-linger <user>
```
  .
Verify with:
- ```
openclaw gateway status
```
- ```
openclaw status
```
- a local smoke test against
```
MiniMax-M2.1
```
- a Telegram send test
If outbound Telegram send says
```
chat not found
```
, tell the user to open the bot DM and press Start, then retry.

Completion standard

Only call the deployment complete when all of the following are true:

```
openclaw gateway status
```
reports
```
Runtime: running
```
```
openclaw status
```
shows Telegram
```
ON
```
and
```
OK
```
A local agent test returns through
```
MiniMax-M2.1
```
A Telegram test message can be delivered after the user has started the bot
The service remains active after SSH disconnect because linger is enabled

Output style

When reporting progress or completion:

State what was installed
State the configured model and provider endpoint
State the Telegram bot username
State the last blocking issue, if any
End with the exact next user action if a manual Telegram step is still required