Basic Information
| Item | Details |
|---|
| Product Name | OpenClaw Issue Tracking System |
| Product Type | Issue Tracking and Project Management System |
| Platform | GitHub Issues |
| Open Issues | 9,574+ |
| Auxiliary Tool | OpenClaw gh-issues Skill (Automated Classification) |
| Community Repository | openclaw/community |
Product Overview
OpenClaw's Issue Tracking System is built on GitHub Issues and serves as the core platform for bug reporting, feature requests, discussions, and community management. The system, in conjunction with OpenClaw's own gh-issues skill, enables partial automated management and is a vital component of community participation and project governance.
System Architecture
Dual Repository Strategy
| Repository | Purpose |
|---|
| openclaw/openclaw | Core Product Issues (Bugs, Feature Requests, Technical Discussions) |
| openclaw/community | Community-related Issues (Governance, Policies, Non-code Improvements) |
Issue Classification
- Bug Reports - Product defects and abnormal behaviors
- Feature Requests - New features and enhancement requests
- Documentation Issues - Documentation errors or improvement suggestions
- Security Issues - Security vulnerability reports (dedicated security channel)
- Community Improvements - Community policy and process improvements
- Policy Change Requests - Community governance policy adjustments
Automated Management
gh-issues Skill
OpenClaw provides its own GitHub Issue classification skill (gh-issues), which is the second most popular skill on ClawHub, with 1,240 community stars.
- Automatic Labeling - Scans issue titles and bodies, automatically applying labels based on keywords (auth, database, security, etc.)
- Batch Processing - Runs batch operations on existing backlog issues during non-working hours
- Expiration Cleanup - Automatically identifies and closes issues inactive for 30 days
- Real-time Processing - New issues are processed within seconds of creation
- Uses curl and GitHub REST API
- GH_TOKEN environment variable is automatically injected by OpenClaw
- Runs without additional configuration
Community Governance Integration
Issue to PR Workflow
- Community members create issues to report problems or requests
- Maintainers or automated tools classify and label the issues
- Contributors claim issues and create corresponding PRs
- Issues are automatically closed upon PR approval
Triage Mechanism
- Core product issues remain in openclaw/openclaw
- Community-related issues are transferred to openclaw/community
- Security issues are handled through a dedicated security channel
- Skill-related issues are directed to ClawHub
Statistics
| Metric | Data |
|---|
| Open Issues | 9,574+ |
| Issue Response Time | Hours to days (depending on priority) |
| Automated Classification Coverage | Majority of new issues |
| Community Participants | Thousands of global contributors |
Challenges
Scale Challenges
- Managing 9,574 open issues requires significant manpower
- Rapidly growing community leads to more incoming issues
- Balancing automation and manual review is necessary
Quality Challenges
- Identifying and merging duplicate issues
- Filtering low-quality issues
- Rapid response to security-sensitive issues
- Handling multi-language issues
Sources