Install nanobot & First Channel

Rule: Pin the GitHub release you trust, verify checksums when published, then configure one provider and one channel before tools sprawl.

Obtain the runtime

Paths vary by upstream: release binary, cargo install, or Docker image. Follow the README for your chosen repo. Prefer tagged releases for production.

Configure providers

Set API keys via env or config for your LLM providers; enable failover only after a single provider works. Misconfigured circuit breakers hide outages as silent model swaps—log which model answered.

First channel proof

Telegram or Web UI is a common first surface. Restrict allowFrom-style allowlists. Confirm the process binds only where you intend (localhost vs public).

First-week checklist

  1. Binary runs; health endpoint or CLI ping succeeds
  2. One model answers deterministically
  3. One channel with allowlist
  4. Backup config; rotate keys out of git
  5. Enable failover only with monitoring

This column

Last updated: 2026-07-14 · Independent analysis on OpenClaw Roadmap. Verify features on each project’s official site/repo—this space moves fast.