Official repository and releases
Confirm the canonical repository, review releases, read the security policy, inspect issues, and clone a trusted revision.
Explore the repository guide →Independent guide · Official links clearly marked
OpenClaw GitHub: Official Repository, Installation, Skills & Plugins
Start with the official source repository, then choose the guide that matches what you want to do: inspect the code, build from source, add a Git-based skill, or install a plugin.
The official repository is openclaw/openclaw. OpenClawDir is an independent community directory and is not affiliated with the OpenClaw project.
Quick answer: If you only want to use OpenClaw, follow the official installer. Use the GitHub repository when you want to inspect source code, contribute, build an unreleased revision, or develop an integration.
Install OpenClaw from GitHub
Use the official pnpm source workflow, build the Control UI, link the CLI, onboard the Gateway, and update safely.
Follow the source setup →GitHub skills
Understand SKILL.md, inspect dependencies and permissions, then install a reviewed Git repository into your workspace.
Review GitHub skills →GitHub plugins
Check plugin provenance, pin a Git ref, install it, restart the Gateway, and verify the live runtime surface.
Review GitHub plugins →Choose the right destination
What are you trying to find on GitHub?
| Goal | Best starting point | Why |
|---|---|---|
| Use the stable application | Official install guide ↗ | The installer handles the supported runtime and onboarding. |
| Read or contribute to core | openclaw/openclaw ↗ | This is the canonical source repository. |
| Find a reusable skill | OpenClawDir skills or ClawHub ↗ | Compare capabilities before inspecting the source. |
| Extend the runtime | OpenClawDir plugins | Plugins can add tools, channels, providers, hooks, and services. |
Trust before install
How to evaluate an OpenClaw GitHub repository
- 1Confirm the owner and purpose.
Do not assume that a repository using the OpenClaw name is official. Read its README, license, maintainers, releases, and linked documentation.
- 2Read executable code, not only the description.
Skills can guide tool use; plugins execute runtime code. Inspect scripts, dependencies, install hooks, network calls, and credential access.
- 3Prefer a reviewed release or commit.
Pinning a tag or commit makes the source you reviewed reproducible and prevents an unexpected branch update from changing the install.
- 4Verify after installation.
List the installed capability, check diagnostics, and confirm only the tools, hooks, services, or commands you expected are active.
OpenClaw GitHub FAQ
What is the official OpenClaw GitHub repository?
+
The official source repository is github.com/openclaw/openclaw. OpenClawDir is an independent directory and is not the official OpenClaw project.
Should I install OpenClaw from GitHub?
+
Most users should use the official installer or published package. A GitHub source checkout is most useful for contributors, plugin developers, and people testing unreleased changes.
Can OpenClaw install skills and plugins from GitHub?
+
Yes. The OpenClaw CLI supports Git sources for skills and plugins. Review the repository, pin a trusted ref where practical, and verify the installed capability before enabling it.
Is every OpenClaw repository on GitHub official?
+
No. Confirm the repository owner, release history, documentation, and requested permissions. Community projects can be useful, but they should not be treated as official by default.