Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Contributor / Maintainer Start Here

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

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

QueueAllLinked PRNo linked PRWhy pick it
Ready-to-queue fixesalllinked PRno linked PRIssues maintainers have marked as suitable candidates for queued fix work.
Clear-shape fixesalllinked PRno linked PRIssues where the likely implementation path is understood.
Small clear-shape fixesalllinked PRno linked PRSmaller scoped issues with an understood fix shape.
Ready fixes with source reproalllinked PRno linked PRQueueable fixes backed by a source-level reproduction.

Highest priority

PriorityAllLinked PRNo linked PRWhy it matters
P0 emergency issuesalllinked PRno linked PRData loss, security bypass, crash loop, or unusable core runtime.
P1 user-facing issuesalllinked PRno linked PRHigh-priority bugs, regressions, or broken workflows.
Beta blockersalllinked PRno linked PRPlugin beta-release blockers.
Regressionsalllinked PRno linked PRBehavior that previously worked and now fails.
Crash bugsalllinked PRno linked PRProcess exits, hangs, or crash loops.

For Maintainers

Issue priority triage

Priority signalAll open issuesLinked PRNo linked PRQueueable + no linked PR
P0 emergencyalllinked PRno linked PRqueueable + no linked PR
P1 user-facingalllinked PRno linked PRqueueable + no linked PR
P2 backlog priorityalllinked PRno linked PRqueueable + no linked PR
Beta blockeralllinked PRno linked PRqueueable + no linked PR
Regressionalllinked PRno linked PRqueueable + no linked PR
Security impactalllinked PRno linked PRqueueable + no linked PR
Data or message lossalllinked PRno linked PRqueueable + no linked PR

PR readiness

QueueAllUnassignedUnassigned + no risk label
P0 + ready for maintainer lookallunassignedunassigned + no risk label
P1 + ready for maintainer lookallunassignedunassigned + no risk label
Ready for maintainer lookallunassignedunassigned + no risk label
Feature showcaseallunassignedunassigned + no risk label
Platinum or betterallunassignedunassigned + no risk label
Diamondallunassignedunassigned + no risk label
Needs proofallunassignedunassigned + no risk label
Waiting on authorallunassignedunassigned + no risk label
Re-review loopallunassignedunassigned + no risk label
<details> <summary>Appendix: detailed issue filters and labeling guide</summary>

Blocked decisions

Decision queueAllNo linked PRMaintainer action
Needs maintainer reviewallno linked PRDecide whether the issue is queueable, blocked, duplicate, or out of scope.
Needs product decisionallno linked PRSet expected behavior before contributors implement.
Needs security reviewallno linked PRDecide disclosure, scope, and required security proof.
Needs live reproallno linked PRConfirm whether live, Crabbox/Testbox, or manual validation is required.
Needs reporter infoallno linked PRAsk for missing details or close if the issue cannot move forward.

PR risk review

Risk queueAllUnassignedReady for maintainer look
Security boundary riskallunassignedready
Compatibility riskallunassignedready
Message delivery riskallunassignedready
Session state riskallunassignedready
Availability riskallunassignedready
Auth/provider riskallunassignedready
Automation riskallunassignedready

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.
  • 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:

  1. Confirm the issue still reproduces or is still needed.
  2. Add exactly one priority label: P0, P1, P2, or P3.
  3. Add a size label when scope is understood.
  4. Add area labels so contributors can find work they understand.
  5. Add impact labels for user-visible risk and contributor prioritization.
  6. Add clawsweeper:fix-shape-clear when the implementation direction is clear enough to evaluate.
  7. Add clawsweeper:queueable-fix when the issue should be prioritized for contributor or queued fix work.
  8. Remove stale blocker labels once the blocker is resolved.
</details>

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Contributor / Maintainer Start Here