Repository Overview

The main repository is at github.com/openclaw-ai/openclaw.

DirectoryContents
src/openclaw/Core agent engine
packs/Built-in tool packs
tests/Unit and integration tests
docs/Developer documentation
examples/Sample scripts and configs

Contributing

# 1. Fork the repo on GitHub, then clone your fork
git clone https://github.com/YOUR_USERNAME/openclaw.git
cd openclaw

# 2. Create a feature branch
git checkout -b feature/my-improvement

# 3. Install in editable mode with dev extras
pip install -e ".[dev]"

# 4. Make your changes, then run tests
pytest tests/ -v

# 5. Commit and push
git add .
git commit -m "feat: describe your change"
git push origin feature/my-improvement

# 6. Open a Pull Request on GitHub

Filing Issues

  • Bug reports: Use the Bug template. Include OpenClaw version, Python version, OS, and a minimal reproduction.
  • Feature requests: Use the Feature template. Describe the use case before the implementation.
  • Security issues: Email security@openclaw.ai — do NOT open a public issue.
💡

Contribution Workflow

OpenClaw follows the standard fork-and-PR workflow. Here is the full step-by-step:

# 1. Fork on GitHub (click "Fork" button), then clone your fork
git clone https://github.com/YOUR_USERNAME/openclaw.git
cd openclaw

# 2. Add upstream remote to keep your fork in sync
git remote add upstream https://github.com/openclaw-ai/openclaw.git

# 3. Create a feature branch
git checkout -b feature/my-improvement

# 4. Make your changes, then run the test suite
pip install -e ".[dev]"
pytest tests/ -v

# 5. Lint your code (required for PRs to pass CI)
ruff check . --fix
ruff format .

# 6. Commit with a descriptive message
git commit -m "feat: add support for Gemini 2.0 Flash model"

# 7. Push to your fork and open a PR on GitHub
git push origin feature/my-improvement

Good First Issues

New contributors: look for issues labeled good first issue on GitHub. These are scoped tasks that don't require deep knowledge of the codebase. Common types:

  • Documentation improvements (typos, missing examples)
  • Adding a new model name to the supported models list
  • Writing a new test case for an existing feature
  • Translating error messages

Browse Good First Issues →

Bug Report Template

**Describe the bug**
A clear description of what went wrong.

**To reproduce**
Steps to reproduce:
1. Run `openclaw run "..." --file test.txt`
2. Observe error

**Expected behaviour**
What you expected to happen.

**Actual behaviour**
What actually happened (include full error output).

**Environment**
- OS:
- Python:
- OpenClaw:  (`openclaw --version`)
- Provider + model:

**Additional context**
Attach relevant config (sanitize API keys!) or log output.

Releases & Changelog

OpenClaw uses Semantic Versioning: MAJOR.MINOR.PATCH.

  • PATCH (e.g. 1.4.1 → 1.4.2): Bug fixes only — safe to upgrade immediately
  • MINOR (e.g. 1.4.x → 1.5.0): New features, backwards-compatible — upgrade after testing
  • MAJOR (e.g. 1.x → 2.0): Breaking changes — read migration guide before upgrading

Follow releases on GitHub: Repository → WatchCustom → check Releases. You will receive an email notification for every new release.

Notable Community Forks

  • openclaw-docker — Pre-built Docker images for all major releases with production-ready health checks
  • openclaw-web — Community-built web UI wrapper around the OpenClaw CLI
  • openclaw-vscode — VS Code extension integrating OpenClaw into the editor sidebar

Browse all forks: github.com/openclaw-ai/openclaw/forks

GitHub Discussions Guide

  • Q&A — Post a question; mark the best answer to help future readers
  • Ideas — Feature requests with discussion before opening an issue
  • Show and Tell — Share your automations, integrations, and projects
  • Announcements — Read-only; official news and release highlights

Open GitHub Discussions →

Staying Up to Date

Follow these steps to get notified about new OpenClaw releases without checking manually:

  1. Go to the OpenClaw GitHub repository
  2. Click Watch (top right) → Custom
  3. Check only Releases and click Apply

You'll receive a GitHub notification (and email if configured) whenever a new version is tagged.

Useful GitHub Badges for Your Projects


![OpenClaw](https://img.shields.io/badge/powered--by-OpenClaw-9333ea)


[![OpenClaw](https://img.shields.io/github/v/release/openclaw-ai/openclaw)](https://github.com/openclaw-ai/openclaw)

Security Advisories

For security-related updates, watch the repository's Security tab. Critical vulnerabilities are also announced in the #announcements channel on Discord. Never run OpenClaw from an unofficial fork without verifying the source.

Back to Resources overview or continue to Community & Support.