OpenClaw Enters Stabilisation Mode: What It Means for Contributors
The Big News
OpenClaw has officially entered Stabilisation Mode. If you've been watching the repo, you've probably noticed PRs flying in at an incredible pace — roughly one every two minutes at peak. While the community energy is amazing, the maintainer team simply cannot review at that velocity while maintaining quality.
What's Changing?
- New feature requests will be closed (and soon auto-closed)
- Bug reports are still welcome — stability work depends on finding and fixing bugs
- Core contributions are locked down for now
The Good News: You Don't Need Core Access
Here's the thing — OpenClaw was designed to be extensible without touching the core. Most of what you want to build doesn't require a PR:
1. Skills
Most "features" are really just skills. Write one, drop it in your skills folder, done. No PR needed, nothing blocking you. Check out ClawdHub for inspiration and to share what you build.
2. CLIs & Tooling
Build around OpenClaw rather than into it. If your tool talks to the API, it doesn't need to live in the repo. This is how the ecosystem grows sustainably.
3. Your Own Fork
Think of it as your "director's cut" — with TypeScript and fewer studio notes. Genuinely the fastest path if you want full control over the codebase.
When PRs Reopen
When stabilisation mode ends and PRs are welcome again:
- Drop your proposal in #pr-thunderdome-dangerzone on Discord first
- Read the channel topic carefully
- Be prepared to compete with thousands of others
- Make sure what you've built is genuinely great
Why This Matters
A more stable core means a better platform for everyone to build on. The maintainers are focusing their energy on making OpenClaw rock solid, which benefits the entire ecosystem.
This is a sign of maturity, not a slowdown. The project has grown to the point where quality control is essential.
Get Involved
- Found a bug? Report it! Stability work depends on your bug reports.
- Have a feature idea? Build it as a skill first. If it proves valuable, it might get promoted to core later.
- Want to help? Focus on documentation, testing, and community support.
Based on GitHub Issue #5799 — 66 reactions and counting.
Comments (0)
No comments yet. Be the first to comment!