I work on Aplite, a managed OpenClaw host. Everything below about OpenClaw itself comes from the upstream docs and is linked to them; the hosted path at the end is ours, with the trade-off stated.
Search for what is openclaw and the first page answers three different questions.
Wikipedia tells the story: an Austrian developer, four names in two months, a star count.
The official docs explain the architecture: trust boundaries, runtimes, a WebSocket
protocol. Hosting companies explain it on a page that ends at their control panel. None
of them says in plain words what the thing is, what the five words in every tutorial
mean, and what it will and will not do. This page does, with the terms as the
OpenClaw docs use them, read on 20 October 2026.
The short version
OpenClaw is an open-source program that you run on a computer you control, and that turns
an AI model into an assistant you message from the chat apps you already use. The docs'
own line: "an open-source AI assistant that runs on your own hardware and meets you in
every chat app you already use."
Open source: the code is on GitHub under the
MIT license, about 393,000 stars on 20 October 2026, stewarded by the OpenClaw
Foundation, a US non-profit that sells nothing ("No subscription. No hosted tier. No
token." on openclaw.ai). You run it: on a laptop, a Mac mini or
a rented server, and only while that machine is on. An AI model: OpenClaw contains
none. It connects to one, from Anthropic, OpenAI, Google and others through a key or a
subscription login, or a local model through Ollama. The model thinks; OpenClaw is
everything around it: the chat connections, the memory on disk, the tools, the schedule.
The current release is 2026.10.5.
The five words
Gateway. The one process that runs all the time: it holds the connections to your
chat apps, serves the browser dashboard, runs the scheduler and talks to the model, on
port 18789 of the machine itself by default
(architecture). When it is down,
nothing answers; a message sent while your laptop sleeps waits until it wakes. That is
why "where does the gateway run" is the first practical question.
Agent. A configured assistant with its own folder, default model and history. The
folder, the workspace, holds plain markdown you can edit: AGENTS.md for operating
instructions, SOUL.md for persona, USER.md for who you are, MEMORY.md for long-term
memory (agent). A fresh install has one agent,
main; more can be added, with different chats routed to each
(multi-agent).
Session. A conversation. By default every direct message from every channel lands in
one rolling conversation, the main session, so what you said in Telegram is known when
you continue in the browser; groups get their own, and scheduled jobs start fresh ones
(sessions).
Skills. Instructions for a specific job: a folder with a SKILL.md that names the
skill and says when and how to use which tools
(skills). Some ship with OpenClaw, some you
write, some you install from ClawHub, the public registry, with
openclaw skills install @owner/<slug>; the docs call a third-party skill untrusted
code, to be read first.
Channels. Where messages come in and go out. Telegram and the browser's WebChat are in
the core install; Discord, Slack, WhatsApp, Signal, iMessage, Matrix, Microsoft Teams,
Google Chat and a dozen more are official plugins
(channels). An unknown sender gets a pairing code
instead of an answer until you approve them.
Four more, briefly: tools, what the agent can do (read, write, exec,
browser, web_search; tools); memory,
MEMORY.md plus dated notes in memory/, so it remembers only what it wrote down
(memory); cron jobs, a prompt on a
schedule delivered to a channel (automations); the
heartbeat, a check every 30 minutes by default, silent when nothing needs attention
(heartbeat).
What it does, and what it does not
It answers in your chat apps; reads and writes files in its workspace; runs commands on
its machine; opens a browser; searches the web; remembers across days in files you can
read; messages you first, on a schedule or when a heartbeat finds something; runs several
agents and sub-agents. The docs' own examples: inbox and calendar briefings, research,
reminders, browser automation, a task sent from your phone
(FAQ).
What it does not do, from the same sources:
- It has no model of its own. You bring a provider key, a ChatGPT or Claude subscription login, or a local model; the model is where the bill comes from. Every path, including the free ones: OpenClaw without an API key.
- It does not run while its machine is off. Sleep, network drops and OS updates stop the gateway; the upstream FAQ says to use a VPS after disconnects (providers and hosting). The free ways of keeping it on: OpenClaw hosting for free.
- It is not locked down by default. Sandboxing and exec approvals are off until you turn them on, and one gateway is one trust domain: "a trusted single-operator assistant" (why OpenClaw, security).
- It is not a coding IDE. The docs say Claude Code or Codex is better for fast coding inside a repository; OpenClaw is the assistant around them, and can run both as its agent runtime (agent runtimes).
- It is not a hosted service. Hosting is what third parties sell, seventeen of them in October 2026; the hosted path below is one.
How it differs from a chat with a model
ChatGPT, Claude.ai and Gemini are a model behind a website: you go to it, the
conversation lives there, and it touches what the vendor connected. OpenClaw inverts
that: the assistant comes to the messenger you already have open, its memory is files on
your disk, its hands are tools on your machine, and it acts on a schedule without being
asked, which no chat tab does. The model is a setting: /new <model> switches it
mid-conversation, and an agent can fail over to a second provider. The price is that you
operate it: machine, keys, updates and security are yours.
Beside it in the same search: Hermes Agent
by Nous Research, the same shape, self-hosted and messaging-first; and Claude Code and
Codex, coding harnesses OpenClaw can drive rather than replace.
How to try it
Install it
About five minutes, by the upstream
getting started page.
Have Node 24.16 or newer, or 26.1 or newer (the installer adds it when missing)
and a model: a provider key, a Claude Code or Codex login, or Ollama.-
Install. macOS, Linux or WSL2:
curl -fsSL https://openclaw.ai/install.sh | bashWindows, in PowerShell:
iwr -useb https://openclaw.ai/install.ps1 | iexDesktop apps: install page.
Onboard. The installer opens the wizard; Quick start finds your login or key,
verifies it with a real completion and opens the dashboard.-
Keep it running. Press Ctrl+C in the foreground gateway, install it as a
service, then check it:
openclaw gateway install openclaw gateway statusThe second command should show the gateway listening on port 18789.
Talk to it.
openclaw dashboardopens the Control UI; type a message. From your
phone, Telegram is the fastest channel:
OpenClaw in Telegram in five minutes.
If something fails, openclaw doctor reads the findings.
Without installing anything
Aplite runs a standard OpenClaw instance for you: one gateway in its own
container on our server, currently 2026.9.8, set up from the browser. Create an account
with email or Google, no card on the Free plan; pick an agent, press Deploy; about a
minute later the workspace opens and you ask. No key to paste: models come through one
metered account, billed in credits, 1 credit = 1¢, token usage under each reply. On top
sit a markdown workspace the agent reads and writes, an approval queue for its changes,
and Telegram from a bot token. What a managed instance gives up, the shell, raw
openclaw.json, local models and day-one releases, is on the
OpenClaw page; other hosts are in
Managed OpenClaw hosting compared. Aplite is
independent and not affiliated with the OpenClaw project.
FAQ
What is OpenClaw?
An open-source AI assistant you run on your own computer or server: it connects a model
of your choice to your chat apps, gives it tools such as files, shell, browser and web
search, keeps its memory in markdown files, and can act on a schedule.
Is OpenClaw free?
The software is free and the project sells nothing. Running it costs a machine that stays
on and the model, billed per token unless it runs locally
(OpenClaw hosting for free).
Do I need an API key to use OpenClaw?
Self-hosted, yes, or a substitute: a ChatGPT or Claude subscription login that onboarding
reuses, or a local model through Ollama. On a managed host that holds the model account,
Aplite among them, there is no key.
How does OpenClaw work?
The gateway stays running. A message from a chat app goes to an agent with its
instructions, memory and skills; the agent calls the model, runs the tools the answer
needs, and the reply returns through the same channel. Scheduled jobs and the heartbeat
start the same loop without a message.
Who makes OpenClaw, and is it owned by OpenAI?
Peter Steinberger published it in late 2025 as Clawdbot, renamed Moltbot and then
OpenClaw in January 2026 (Wikipedia); the
OpenClaw Foundation, an independent non-profit funded by donations, stewards it since he
joined OpenAI in February 2026. OpenAI is one donor; the docs say donors do not control
the project and no lab's model is privileged in the code.
Top comments (0)