VarwoOpenClaw: Official Setup Route, Gateway and Access Choices
Find the official OpenClaw project and documentation, understand the Gateway and model access, and choose a limited first setup before connecting chat accounts.
Official website · GitHub repository · Getting started
OpenClaw is an open-source AI assistant system that connects model access, tools and chat channels through a Gateway. Use the official website’s documentation and repository links to establish which project you are installing. Similar domain names in search results are not proof of a shared operator.
Sources checked November 3, 2026. This is a setup decision guide. We have not installed OpenClaw, connected an account, run a model request or tested its isolation controls.
Understand the pieces
| Piece | What to decide |
|---|---|
| Gateway | Which machine runs and manages the assistant |
| Model access | Which supported account or provider supplies inference |
| Dashboard | How you will inspect and interact with the local setup |
| Chat channel | Which account and conversations you intend to connect |
| Tools and skills | Which tasks the assistant is permitted to perform |
The official documentation lists channel options including Telegram, WhatsApp, Discord and others. Connecting a channel is a separate setup step; installing the software does not demonstrate that your account is already connected or that every feature is available.
Start with one controlled task
The getting-started guide describes Quick start and Custom setup. Quick start can reuse detected AI access and verifies it with a real completion; Custom setup provides the guided choices. This means onboarding itself may use an existing provider allowance. Check the selected route and its billing conditions first.
Follow the current operating-system and runtime requirements in that guide. Keep the initial Gateway in the foreground while you confirm that the dashboard works; decide separately whether it should become a background service. Use one non-sensitive task with an answer you can check before connecting additional chat accounts or enabling recurring actions.
Local hosting and access boundaries
The trust-boundary documentation says the Gateway holds channel connections, configuration and credentials, and binds to loopback by default. It also distinguishes the Gateway from configured isolated execution and notes that sandboxing is off by default. Local installation therefore does not, by itself, establish that every tool call runs in a sandbox or that model processing stays on your computer.
Before expanding a setup, identify the active execution location, account scope and approval behavior for actions that write or send information. Verify those settings in your installation rather than inferring them from a product description. If you only need information about a coding assistant, start with Claude Code; OpenClaw’s connected-channel workflow is a different operational choice.