Files
openclaw/docs/platforms/index.md
Vincent Koc 82fd83418e docs: replace ampersand headings for stable Mintlify anchors
Per docs/CLAUDE.md, Mintlify anchor generation is brittle for headings
that contain em dashes, apostrophes, and ampersands. Normalize 9 H2
headings across docs/date-time.md, docs/pi.md, docs/platforms/{index,
macos, mac/webchat, mac/peekaboo}.md, docs/nodes/{images,audio}.md, and
docs/reference/AGENTS.default.md from `X & Y` to `X and Y` so anchors
do not collapse on entity decoding. Verified no inbound anchor references
to the renamed sections in the docs tree.
2026-05-05 16:33:00 -07:00

2.1 KiB

summary, read_when, title
summary read_when title
Platform support overview (Gateway + companion apps)
Looking for OS support or install paths
Deciding where to run the Gateway
Platforms

OpenClaw core is written in TypeScript. Node is the recommended runtime. Bun is not recommended for the Gateway — known issues with WhatsApp and Telegram channels; see Bun (experimental) for details.

Companion apps exist for macOS (menu bar app) and mobile nodes (iOS/Android). Windows and Linux companion apps are planned, but the Gateway is fully supported today. Native companion apps for Windows are also planned; the Gateway is recommended via WSL2.

Choose your OS

VPS and hosting

Gateway service install (CLI)

Use one of these (all supported):

  • Wizard (recommended): openclaw onboard --install-daemon
  • Direct: openclaw gateway install
  • Configure flow: openclaw configure → select Gateway service
  • Repair/migrate: openclaw doctor (offers to install or fix the service)

The service target depends on OS:

  • macOS: LaunchAgent (ai.openclaw.gateway or ai.openclaw.<profile>; legacy com.openclaw.*)
  • Linux/WSL2: systemd user service (openclaw-gateway[-<profile>].service)
  • Native Windows: Scheduled Task (OpenClaw Gateway or OpenClaw Gateway (<profile>)), with a per-user Startup-folder login item fallback if task creation is denied