Skip to content
Guides

OpenClaw on GitHub

The repository, the organisation, the releases, and how to read them

5 min read

The OpenClaw repository lives at github.com under the openclaw organisation, in a repository of the same name, and it has been there since the rename on January 30, 2026. It is the source, the issue tracker, the releases page and, for some install methods, the install source itself. Here is what the organisation holds, how to read a release, and what to do with the repository if you are not a contributor.

What is where

  • The main repository: the Gateway, the CLI, the Control UI and the bundled skills and plugins, MIT-licensed and stewarded by the OpenClaw Foundation.
  • The Windows companion repository, which publishes the signed Windows Hub installers for x64 and ARM64.
  • The releases page of the main repository, which carries the macOS app as a dmg or zip when a release ships those assets; some releases only ship CLI, evidence or Windows assets, so you take the newest one that has what you need.
  • The docs, at their own domain since the rename.

Installing from the repository is documented three ways: clone, build with pnpm and link the CLI to the checkout; run the installer with the git method pointed at the main branch; or switch an existing install between the stable package channel and the dev channel with the update command. Each gives you the latest and greatest, and each hands you the update discipline the packaged releases handle for you.

Open source, open to everyone.

How to read a release

  • The assets tell you the platforms: a dmg or zip for the Mac app, installers in the Windows repository, and the npm package for everything else.
  • Updates regularly break things that worked last week, as one user put it; the updating guide covers the rollback path and the doctor command that migrates retired settings.
  • The trust envelope for skills is a registry feature, not a GitHub one: a skill installed from a Git repository is refreshed by reinstalling, and verification only exists for registry installs.

What GitHub is not

It is not where skills live; that is the registry, What is ClawHub. It is not where the community gathers day to day; that is Discord and the showcase. And an official-looking profile claiming a title at OpenClaw is, by the project’s own account of the rename, more likely a scam than a maintainer; Clawdbot, Moltbot, OpenClaw tells that story.

If you are not a contributor

You do not need the repository. The installer, the packaged releases and the desktop apps cover every platform, and Updating OpenClaw covers keeping them current. Hosted OpenClaw on Diali is the version where the release channel, the update timing and the rollback are handled on an isolated instance, tested on our own assistants first.

  • One organisation, two repositories that matter, one releases page.
  • Source installs are for contributors and the impatient.
  • Skills and community live elsewhere; scams live everywhere.
Get started

Stop reading about it, build one

Set up an agent, pick a channel, and have it working inside the app you already keep open.