Community

Discord

The primary community hub. Join for real-time help, show-and-tell, and release announcements.

• #general — introductions and general chat
• #help — get answers to your OpenClaw questions
• #showcase — share your automations and workflows
• #dev — core development discussion

Reddit

Long-form Q&A, tutorials, and news at r/openclaw.

Twitter / X

Follow @openclaw_ai for release announcements and tips.

GitHub Discussions

For feature requests, RFCs, and long-running design discussions: GitHub Discussions.

Code of Conduct

All community spaces follow the Contributor Covenant. Be respectful and constructive.

How to Get the Best Help

Getting your question answered quickly depends on where you ask and how you ask it. Here is the decision tree:

• Something is broken / crashing → GitHub Issues — include your OS, version (openclaw --version), and the full error message
• How do I do X? → Discord #help channel — fastest human response
• I have an idea / feature request → GitHub Discussions
• I want to share a cool automation → Discord #showcase or GitHub Discussions: Show and Tell

Discord Channel Guide

Writing a Good Bug Report

A good bug report includes:

**Environment**
- OS: Ubuntu 24.04
- Python: 3.12.2
- OpenClaw: 1.4.1 (`openclaw --version`)

**What I did**
```
openclaw run "Summarise README.md" --file README.md
```

**What I expected**
A summary of the file.

**What happened**
```
Error: FileNotFoundError: [Errno 2] No such file or directory: 'README.md'
```

**Notes**
The file exists in the current directory. Running `ls README.md` confirms it.

Community Events & Office Hours

The OpenClaw community runs regular virtual events open to everyone:

• Monthly Office Hours — First Thursday of each month, 18:00 UTC. Core team answers questions live on Discord stage
• Community Demo Day — Last Friday of each month. Members present their automations (5 min slots, sign up in Discord)
• Release Walkthroughs — After major releases, a live walkthrough of new features in Discord

All events are recorded and posted to the Videos page within 48 hours.

Code of Conduct Summary

• Be respectful and patient — everyone is at a different experience level
• No spam, self-promotion without context, or off-topic LLM vendor debates
• Do not share other people's API keys or tokens, even as examples
• Violations → warn → temp mute → permanent ban at moderator discretion

Full Code of Conduct: CODE_OF_CONDUCT.md on GitHub.

Support Channels at a Glance

Security Disclosures

If you discover a security vulnerability in OpenClaw, please do not open a public GitHub issue. Instead, email security@openclaw.top with:

• A clear description of the vulnerability
• Steps to reproduce
• Potential impact and attack scenario
• Your suggested fix (optional)

You will receive a response within 48 hours. Confirmed vulnerabilities will be credited in the release notes unless you prefer anonymity.

Contributing to the Community

• Answer questions in Discord #help — the best way to deepen your own understanding
• Share your automations in #showcase or GitHub Discussions: Show and Tell
• Write a tutorial and submit it to the community tutorials thread
• Translate the docs — see the i18n guide
• Contribute code — see GitHub Resources for the contribution workflow

Contributing to the Community

The OpenClaw community grows through contributions of all kinds — not just code. Here are the most impactful ways to help:

See the full contribution guide at OpenClaw GitHub Resources.