README and install
Start with the root README for supported installation paths, quick-start commands, architecture links, and the source-build workflow.
Read README.md ↗Repository intent
The canonical OpenClaw source lives at github.com/openclaw/openclaw. Use this guide to navigate the project without confusing the official repository with community skills, plugins, or directories.
git clone https://github.com/openclaw/openclaw.git
cd openclaw
git remote -v
The final command should show github.com/openclaw/openclaw as the origin. If you are reviewing a community fork, keep the upstream repository visible so you can compare changes.
Repository map
Start with the root README for supported installation paths, quick-start commands, architecture links, and the source-build workflow.
Read README.md ↗Use published releases for version notes and reproducible revisions. A tag is easier to audit than a moving development branch.
Browse releases ↗Search existing reports before opening a bug. Setup questions are usually better directed to the community support channels linked by the project.
Search issues ↗Do not post a vulnerability as a public issue. Follow the official SECURITY.md instructions for responsible disclosure.
Read SECURITY.md ↗| Use case | Recommended path |
|---|---|
| You want a stable personal assistant | Use the official installer ↗. |
| You want to contribute to core | Clone the repository and follow CONTRIBUTING.md ↗. |
| You are developing an external capability | Prefer a plugin workflow when the capability does not need a core change. |
| You want an unreleased fix | Review the exact commit, understand the risk, and keep a rollback path. |