PicoClaw on Raspberry Pi: Setup Guide for Clawbot & OpenClaw AI Assistants - Deploy your own tiny, fast AI automation bot

The Problem

You installed PicoClaw, the tiny, fast, and deployable anywhere, Clawdbot-inspired AI assistant to automate the mundane and unleash your creativity, on a Raspberry Pi. It works great, until you disconnect from SSH and it stops. Or your Pi loses network because the Ethernet chip went to sleep to save power.

This guide fixes that.

1. Put the binary in the right place

The issue: Your binary lives in /home/pi/picoclaw. That's fine for testing. But it's not where Linux expects user programs to be.

The fix:

sudo cp /home/pi/picoclaw /usr/local/bin/picoclaw
sudo chmod +x /usr/local/bin/picoclaw

Why: /usr/local/bin is where custom software goes. System services expect to find executables there. It's the convention.

2. Make it run forever (systemd service)

The issue: Running ./picoclaw gateway in an SSH session dies when you disconnect. You need it to run in the background, automatically, even after a reboot.

The fix:

Create /etc/systemd/system/picoclaw.service:

[Unit]
Description=PicoClaw Gateway
After=network.target

[Service]
Type=simple
User=pi
WorkingDirectory=/home/pi
ExecStart=/usr/local/bin/picoclaw gateway
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

Then tell systemd about it:

sudo systemctl daemon-reload
sudo systemctl enable picoclaw
sudo systemctl start picoclaw

Why:

• Type=simple: PicoClaw runs in the foreground, systemd watches the process
• Restart=always: If it crashes, it restarts
• enable: Starts automatically on boot
• User=pi: Runs as your user, not root

Check it's running:

sudo systemctl status picoclaw

3. Stop the network card from sleeping

The issue: The Raspberry Pi's Ethernet (bcmgenet) and WiFi (brcmfmac) adapters have power saving enabled by default. They go to sleep when idle. When they wake up, they may not reconnect properly, especially on Pi 3B+ and Pi 4.

You know this happened if your Pi goes silent and dmesg shows:

bcmgenet fd580000.ethernet eth0: link down

The fix:

Edit /boot/firmware/cmdline.txt (note: not /boot/cmdline.txt. This varies by Pi model and OS):

Add this to the single line (keep everything else on that line):

psci=force_on

That enables ARM Power State Coordination Interface, which helps keep things awake.

Then disable WiFi power saving:

echo "options brcmfmac roamoff=1 feature_disable=0x82000" | sudo tee /etc/modprobe.d/brcmfmac.conf

Reboot:

sudo reboot

Why:

• psci=force_on: Keeps the ARM power management cooperative
• WiFi power saving causes dropouts on many Pi models. This disables it

4. Verify everything works

# Check service is running
sudo systemctl status picoclaw

# Check for power save issues in logs
dmesg | grep -i "power\|sleep\|wol"

# Check network is stable
ip link show
ping -c 3 8.8.8.8

Summary

Why this matters

A personal AI assistant should be always on. You don't want to SSH in just to start it. You don't want it going offline because a network chip napped.

These three changes (binary location, systemd service, power management) make your Pi a reliable server instead of a finicky toy.

That's it.

Resources

Picoclaw repo: https://github.com/sipeed/picoclaw
Picoclaw releases: https://github.com/sipeed/picoclaw/releases