Follow the Windows setup guide, then test your first OpenClaw reply.
A practical beginner guide to installing the Windows desktop app, letting it prepare a local Gateway, connecting one AI provider, and getting your first useful reply.
Goal: install the official Windows app, finish local setup, connect one model provider, and send one safe test message in the app.
Windows Hub is OpenClaw’s native Windows desktop app. You open it as OpenClaw Companion. It provides setup, tray status, native chat, and diagnostics. Its local setup prepares the background Gateway that connects your app to your AI provider.
The app creates its own OpenClawGateway environment using Windows Subsystem for Linux (WSL). You do not need to install a separate Ubuntu distribution or prepare developer tools first. Follow the required steps below; add extra features after chat works.
The app also needs Microsoft WebView2, already present on Windows 11 and most updated Windows 10 PCs. If it is reported missing, use the Microsoft link in troubleshooting on page 6.
The official site is your download entry point; GitHub hosts the installer file. The buttons go directly to the file—no release hunting is needed. If a download fails, follow the Hub link in the official Windows docs. Optional desktop/startup shortcuts are your choice.
| Screen or prompt | What to do |
|---|---|
| Security notice / Welcome | Read the notice and confirm this is your trusted PC. Choose Set up locally (also described as Install a local gateway (WSL)). |
| WSL readiness | Follow any WSL setup request, approve the required administrator prompt, and restart Windows if asked. Reopen Companion to continue. If virtualization is blocked, resolve that specific issue first. |
| Capabilities | Review the profile, permissions, and install summary. Leave optional camera, microphone, screen capture, and system-control access off unless you intend to use them. Defer Local AI/model downloads. |
| Local setup progress | Let the app create OpenClawGateway and install its Gateway runtime. It does not modify your existing Ubuntu distro. |
| Gateway installed | Choose Start OpenClaw onboard for provider/model setup in Step 4. |
Choose an existing Gateway only if you already operate one. If you see Install new WSL Gateway with a deletion/replacement warning, stop: that is not a fresh install. Use the existing connection or get help before replacing its data.
The OpenClaw onboard screen presents setup questions from your Gateway. Exact choices can vary with its version. Select one provider you intend to use, complete its sign-in or API-key prompts, and finish any model check before moving on.
OpenClaw supports ChatGPT/Codex subscription sign-in through its OpenAI provider. If you already have eligible access, choose the OpenAI option and its Codex / ChatGPT subscription sign-in method when offered, rather than the API-key method.
Choose your supported provider and model, then follow the login, OAuth, device-code, token, or API-key method shown. Account and billing requirements differ. Put an API key only in the designated setup/settings field, not ordinary chat. If you need help choosing, use SAGE9AI AgentLens.
When a connection check fails, read the error and retry or explicitly choose another provider. Do not assume a detected account is already authorized. Hub’s Gateway runs inside WSL, so a provider login on Windows may not be available there automatically.
Skip optional channels, memory imports, hooks/webhooks, plugins, MCP, local-model downloads, and remote access. Add them after your first reply. Keep the required Gateway and authentication enabled.
On All set, review Launch at startup and choose Finish. The tray icon should turn green when connected. A green icon confirms the Gateway connection; your first chat in Step 5 confirms the AI can answer.
After your first successful app chat, you can use the web dashboard in Edge, Chrome, or another browser. Choose Open Dashboard from Companion’s tray menu. It opens the browser Control UI for the connected Gateway.
This is another view of the same Gateway, not another installation. If you prefer the app, skip it. Use the app’s action rather than guessing an address or installing a second Gateway. Browser access can require authentication or pairing even when the native app already works.
The Gateway is your agent’s background connection hub. A Gateway token is a private access credential, not a model-provider API key. An app-generated dashboard link may contain a token; keep the whole link private.
A setup snag does not mean you did anything wrong. Windows settings, network access, and existing tools vary. Note the exact error and work through one issue at a time.
| What happened | Try this first |
|---|---|
| Installer will not open | Check Windows version and System type. Download the matching file again through the official install page. Do not disable antivirus or SmartScreen. |
| WSL / virtualization error | Follow the readiness message. Approve required Windows feature setup and restart if requested. Ask your PC/IT administrator if virtualization or policy blocks it. |
| WebView2 is missing | Get Microsoft’s WebView2 Evergreen Standalone Installer, then reopen Companion. |
| Tray icon is missing | Look under the ^ hidden-icons arrow, or open OpenClaw Companion from Start. |
| Gateway connects but chat does not answer | Revisit provider/model setup. Check login, account access, quota or API billing. Do not add extra tools to fix model authentication. |
| Local setup or onboarding fails | Read Command Center or the setup log offered by Hub. Use the Windows troubleshooting docs. Do not reinstall over an existing Gateway without reviewing its data warning. |
Use ChatGPT or another AI assistant you already have access to. Paste the exact error or upload a photo/screenshot, include your Windows version and the guide step that failed, and ask for beginner-friendly help one step at a time. AI can often help with one-off setup issues.
For the best results: share the error and relevant setup details, keeping passwords, API keys, Gateway tokens, device codes, and personal information out of your message or screenshot. Ask it to explain each suggested step.
Once app chat works, ask OpenClaw to help you add communications or another useful feature. Start with one messaging app, such as Telegram, Slack, Discord, or WhatsApp. Each has its own account, pairing, and permission requirements.
You complete account sign-in and approvals when needed. Enable only the capabilities you want; keep pairing, allowlists, and tool permissions in place.
Official sources checked September 18, 2026: Downloads · Windows · Hub setup · Hub onboarding · OpenAI access · Control UI. App labels and available providers can change between releases.