Labels

• bug

  bug

  Something isn't working

• clawsweeper:needs-info

  clawsweeper:needs-info

  ClawSweeper needs more reporter information before it can verify this issue.

• clawsweeper:needs-live-repro

  clawsweeper:needs-live-repro

  ClawSweeper needs live local, crabbox, or manual validation to confirm this issue.

• clawsweeper:needs-maintainer-review

  clawsweeper:needs-maintainer-review

  ClawSweeper marked this issue as needing maintainer review before automation.

• clawsweeper:needs-product-decision

  clawsweeper:needs-product-decision

  ClawSweeper marked this issue as needing a product or behavior decision.

• clawsweeper:needs-security-review

  clawsweeper:needs-security-review

  ClawSweeper marked this issue as needing security-sensitive review.

• clawsweeper:no-new-fix-pr

  clawsweeper:no-new-fix-pr

  ClawSweeper does not recommend queueing a new automated fix PR for this issue.

• clawsweeper:source-repro

  clawsweeper:source-repro

  ClawSweeper found a high-confidence source-level issue reproduction.

• documentation

  documentation

  Improvements or additions to documentation

• duplicate

  duplicate

  This issue or pull request already exists

• enhancement

  enhancement

  New feature or request

• feature: ✨ showcase

  feature: ✨ showcase

  ClawSweeper spotlight: unusually compelling feature idea for maintainer attention.

• good first issue

  good first issue

  Good for newcomers

• help wanted

  help wanted

  Extra attention is needed

• impact:other

  impact:other

  This issue has meaningful maintainer-visible impact outside the owned taxonomy.

• impact:security

  impact:security

  This issue is about security boundaries, credentials, authz, sandboxing, or sensitive data.

• impact:session-state

  impact:session-state

  This issue is about session, memory, transcript, context, or agent state drift.

• invalid

  invalid

  This doesn't seem right

• issue-rating: 🐚 platinum hermit

  issue-rating: 🐚 platinum hermit

  Good issue quality with a plausible reproduction path needing some confirmation.

• issue-rating: 🦐 gold shrimp

  issue-rating: 🦐 gold shrimp

  Decent issue quality, but reproduction details are still incomplete.

• issue-rating: 🦞 diamond lobster

  issue-rating: 🦞 diamond lobster

  Very strong issue quality with high-confidence source-level or clear reproduction.

• issue-rating: 🦪 silver shellfish

  issue-rating: 🦪 silver shellfish

  Thin issue quality; more reproduction proof or environment detail is needed.

• merge-risk: 🚨 auth-provider

  merge-risk: 🚨 auth-provider

  🚨 Merging this PR could break OAuth, tokens, provider routing, model choice, or credentials.

• merge-risk: 🚨 automation

  merge-risk: 🚨 automation

  🚨 Merging this PR could break CI, automerge, proof capture, label sync, or automation.

• merge-risk: 🚨 availability

  merge-risk: 🚨 availability

  🚨 Merging this PR could cause crashes, hangs, restart loops, stalls, or process outages.

• merge-risk: 🚨 compatibility

  merge-risk: 🚨 compatibility

  🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades.

• merge-risk: 🚨 message-delivery

  merge-risk: 🚨 message-delivery

  🚨 Merging this PR could drop, duplicate, misroute, suppress, or wrongly target messages.

• merge-risk: 🚨 security-boundary

  merge-risk: 🚨 security-boundary

  🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data.

• merge-risk: 🚨 session-state

  merge-risk: 🚨 session-state

  🚨 Merging this PR could lose, corrupt, stale, or mis-associate session or agent state.

• P0

  P0

  Emergency: data loss, security bypass, crash loop, or unusable core runtime.