Files
Charles c81aee5a96 docs: add ChromeOS (Crostini) platform install guide (#107663)
* docs: add ChromeOS (Crostini) platform install guide

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: correct ChromeOS Linux container setup path

* docs: add zh-CN glossary entries for ChromeOS page terms

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Patrick Erichsen <patrick.a.erichsen@gmail.com>
2026-08-04 15:41:42 -07:00

2.4 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 required runtime because the canonical state store uses node:sqlite. Bun remains available for dependency installation and package scripts; see Bun.

Companion apps exist for Windows Hub, macOS (menu bar app), and mobile nodes (iOS/Android). Linux companion apps are planned, but the Gateway is fully supported today. On Windows, choose Windows Hub for the desktop app, native PowerShell install for terminal-first use, or WSL2 for the most Linux-compatible Gateway runtime.

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> for a named profile)
  • 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