Practical guidance repo for anyone who wants to try OpenClaw on a Raspberry Pi.
This project focuses on:
- fast first-time setup
- reproducible scripts instead of one-off commands
- operational reliability (health checks, logs, restart flows)
- performance visibility (benchmarks, temperature, throttling)
If this is your first time:
- Read
docs/START_HERE.md - Run
docs/QUICKSTART.md - Use
docs/OPERATIONS.mdfor daily usage
git clone https://github.com/sulimanbadour1/OpenClaw_raspberry.git
cd open_claw_raspberry
cp .env.example .env
nano .env
chmod +x scripts/*.sh
./scripts/bootstrap_full.sh --env-file .env- Bootstrap and setup automation:
scripts/setup_pi_openclaw.sh,scripts/bootstrap_full.sh - Runtime/service management:
scripts/stack.sh,scripts/healthcheck.sh - Environment and secret handling:
scripts/configure_env.sh,.env.example,SECURITY.md - Performance and thermal tools:
scripts/benchmark_openclaw.py,scripts/pi_telemetry.sh,scripts/optimize_openclaw.sh - Optional diagnostics UIs:
openclaw_model_monitor.py,check_openclaw_pi5.py
make help
make health
make benchmark
make telemetry
make tune-show
make checkdocs/START_HERE.mddocs/QUICKSTART.mddocs/INSTALL_PI.mddocs/CONFIGURATION.mddocs/OPERATIONS.mddocs/TROUBLESHOOTING.mddocs/FAQ.mddocs/LOCAL_LLM_CATALOG.mddocs/BENCHMARKING.mddocs/PERFORMANCE_TUNING.mddocs/PI_OPENCLAW_GENERAL.mdSECURITY.mdCONTRIBUTING.md
- Never commit real secrets.
- Keep runtime keys in local
.envand service overrides. - Follow
SECURITY.mdchecks before pushing.
- Local:
make repo-healthmake security-checkmake check
- CI:
.github/workflows/validate.yml.github/workflows/health-security.yml(includes scheduled daily run)
MIT (LICENSE).