This dashboard points contributors and maintainers to the highest-signal OpenClaw work queues. Each issue table includes linked PR and no linked PR views so maintainers and contributors can separate covered work from unclaimed work.
Need discussion or contributor coordination? Join the OpenClaw Discord and use #clawtributors.
For Contributors
Start here
| Queue |
All |
Linked PR |
No linked PR |
Why pick it |
| Ready-to-queue fixes |
all |
linked PR |
no linked PR |
Issues maintainers have marked as suitable candidates for queued fix work. |
| Clear-shape fixes |
all |
linked PR |
no linked PR |
Issues where the likely implementation path is understood. |
| Small clear-shape fixes |
all |
linked PR |
no linked PR |
Smaller scoped issues with an understood fix shape. |
| Ready fixes with source repro |
all |
linked PR |
no linked PR |
Queueable fixes backed by a source-level reproduction. |
Highest priority
For Maintainers
Issue priority triage
PR readiness
Appendix: detailed issue filters and labeling guide
Blocked decisions
| Decision queue |
All |
No linked PR |
Maintainer action |
| Needs maintainer review |
all |
no linked PR |
Decide whether the issue is queueable, blocked, duplicate, or out of scope. |
| Needs product decision |
all |
no linked PR |
Set expected behavior before contributors implement. |
| Needs security review |
all |
no linked PR |
Decide disclosure, scope, and required security proof. |
| Needs live repro |
all |
no linked PR |
Confirm whether live, Crabbox/Testbox, or manual validation is required. |
| Needs reporter info |
all |
no linked PR |
Ask for missing details or close if the issue cannot move forward. |
PR risk review
Ready fixes by impact
- Ready security-impact fixes (no linked PR) - queueable issues touching security boundaries, credentials, authz, sandboxing, or sensitive data.
- Ready data-loss fixes (no linked PR) - queueable issues that can lose, corrupt, or silently drop user/session/config data.
- Ready message-loss fixes (no linked PR) - queueable issues involving lost, duplicated, or misrouted channel messages.
- Ready crash-loop fixes (no linked PR) - queueable issues causing crashes, hangs, restart loops, or process availability failures.
- Ready auth/provider fixes (no linked PR) - queueable issues affecting auth, provider routing, model choice, or SecretRef resolution.
- Ready session-state fixes (no linked PR) - queueable issues affecting sessions, memory, transcripts, context, or agent state.
Clear-shape fixes by impact
Needs maintainer attention
Area filters
Labeling guide
Use these labels to make issues show up in the right dashboard sections:
P0 - emergency: data loss, security bypass, crash loop, or unusable core runtime.P1 - high-priority user-facing bug, regression, or broken workflow.P2 - normal backlog priority with limited blast radius.P3 - low-priority cleanup, docs, polish, ergonomics, or speculative work.clawsweeper:queueable-fix - contributor-ready issue suitable for queued fix work.clawsweeper:fix-shape-clear - the expected fix direction is understood well enough for contributors to evaluate and implement.clawsweeper:source-repro - there is a source-level reproduction that gives contributors a concrete starting point.impact:security, impact:data-loss, impact:message-loss, impact:crash-loop, impact:auth-provider, impact:session-state - the user or operator consequence that should influence priority.size: XS, size: S, size: M, size: L, size: XL - expected implementation size; use smaller sizes for contributor-friendly sorting.regression, bug:behavior, bug:crash, beta-blocker - bug shape and release urgency.feature: ✨ showcase - ClawSweeper spotlight for unusually compelling feature PR ideas that maintainers should notice; this is positive-only and not a merge gate.app:*, channel:*, plugin:*, gateway, cli, docs, security, scripts, commands, docker, tui, agents - primary ownership or work area.clawsweeper:needs-info, clawsweeper:needs-live-repro, clawsweeper:needs-maintainer-review, clawsweeper:needs-product-decision, clawsweeper:needs-security-review - blocked until the named follow-up happens.clawsweeper:human-review - PR needs a human maintainer review before automation or merge handling continues.no-stale - keep long-lived tracking issues, dashboards, and active coordination issues open.
Prefer one priority label, one size label, one issue-shape label, one or more area labels, and one or more impact labels when relevant. Use clawsweeper:queueable-fix for issues contributors should prioritize, and clawsweeper:fix-shape-clear when the issue is understandable enough to pick up but may still need maintainer judgment before queueing.
Maintainer triage checklist
When grooming contributor candidates:
- Confirm the issue still reproduces or is still needed.
- Add exactly one priority label:
P0, P1, P2, or P3.
- Add a size label when scope is understood.
- Add area labels so contributors can find work they understand.
- Add impact labels for user-visible risk and contributor prioritization.
- Add
clawsweeper:fix-shape-clear when the implementation direction is clear enough to evaluate.
- Add
clawsweeper:queueable-fix when the issue should be prioritized for contributor or queued fix work.
- Remove stale blocker labels once the blocker is resolved.
This dashboard points contributors and maintainers to the highest-signal OpenClaw work queues. Each issue table includes
linked PRandno linked PRviews so maintainers and contributors can separate covered work from unclaimed work.Need discussion or contributor coordination? Join the OpenClaw Discord and use
#clawtributors.For Contributors
Start here
Highest priority
For Maintainers
Issue priority triage
PR readiness
Appendix: detailed issue filters and labeling guide
Blocked decisions
PR risk review
Ready fixes by impact
Clear-shape fixes by impact
Needs maintainer attention
Area filters
Labeling guide
Use these labels to make issues show up in the right dashboard sections:
P0- emergency: data loss, security bypass, crash loop, or unusable core runtime.P1- high-priority user-facing bug, regression, or broken workflow.P2- normal backlog priority with limited blast radius.P3- low-priority cleanup, docs, polish, ergonomics, or speculative work.clawsweeper:queueable-fix- contributor-ready issue suitable for queued fix work.clawsweeper:fix-shape-clear- the expected fix direction is understood well enough for contributors to evaluate and implement.clawsweeper:source-repro- there is a source-level reproduction that gives contributors a concrete starting point.impact:security,impact:data-loss,impact:message-loss,impact:crash-loop,impact:auth-provider,impact:session-state- the user or operator consequence that should influence priority.size: XS,size: S,size: M,size: L,size: XL- expected implementation size; use smaller sizes for contributor-friendly sorting.regression,bug:behavior,bug:crash,beta-blocker- bug shape and release urgency.feature: ✨ showcase- ClawSweeper spotlight for unusually compelling feature PR ideas that maintainers should notice; this is positive-only and not a merge gate.app:*,channel:*,plugin:*,gateway,cli,docs,security,scripts,commands,docker,tui,agents- primary ownership or work area.clawsweeper:needs-info,clawsweeper:needs-live-repro,clawsweeper:needs-maintainer-review,clawsweeper:needs-product-decision,clawsweeper:needs-security-review- blocked until the named follow-up happens.clawsweeper:human-review- PR needs a human maintainer review before automation or merge handling continues.no-stale- keep long-lived tracking issues, dashboards, and active coordination issues open.Prefer one priority label, one size label, one issue-shape label, one or more area labels, and one or more impact labels when relevant. Use
clawsweeper:queueable-fixfor issues contributors should prioritize, andclawsweeper:fix-shape-clearwhen the issue is understandable enough to pick up but may still need maintainer judgment before queueing.Maintainer triage checklist
When grooming contributor candidates:
P0,P1,P2, orP3.clawsweeper:fix-shape-clearwhen the implementation direction is clear enough to evaluate.clawsweeper:queueable-fixwhen the issue should be prioritized for contributor or queued fix work.