Skip to content

Labels

Labels

48 labels

  • Awaiting Response

    Awaiting Response
    Awaiting a response from the author

  • clawsweeper:fix-shape-clear

    clawsweeper:fix-shape-clear
    ClawSweeper found a clear likely implementation shape for this issue.

  • clawsweeper:linked-pr-open

    clawsweeper:linked-pr-open
    ClawSweeper found an open linked pull request for 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: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.

  • 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:message-loss

    impact:message-loss
    This issue is about lost, duplicated, misrouted, or suppressed channel messages.

  • impact:other

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

  • impact:ux-friction

    impact:ux-friction
    User-facing flow adds avoidable confusion or support burden without fully blocking progress.

  • issue-rating: 🌊 off-meta tidepool

    issue-rating: 🌊 off-meta tidepool
    Issue quality rating does not apply to this item.

  • issue-rating: 🦞 diamond lobster

    issue-rating: 🦞 diamond lobster
    Very strong issue quality with high-confidence source-level or clear reproduction.

  • 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: 🚨 security-boundary

    merge-risk: 🚨 security-boundary
    🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data.

  • P1

    P1
    Urgent regression or broken agent/channel workflow affecting real users now.

  • P2

    P2
    Normal priority bug or improvement with limited blast radius.

  • P3

    P3
    Low-risk cleanup, docs, polish, ergonomics, or speculative feature.

  • proof: sufficient

    proof: sufficient
    Contributor real behavior proof is sufficient.

  • proof: 📸 screenshot

    proof: 📸 screenshot
    Contributor real behavior proof includes screenshot evidence.

  • question

    question
    Further information is requested

  • rating: 🌊 off-meta tidepool

    rating: 🌊 off-meta tidepool
    PR readiness rating does not apply to this item.

  • rating: 🐚 platinum hermit

    rating: 🐚 platinum hermit
    Good normal PR readiness with ordinary maintainer review expected.

  • rating: 🦐 gold shrimp

    rating: 🦐 gold shrimp
    Decent PR readiness signal, but merge confidence is limited.

  • rating: 🦪 silver shellfish

    rating: 🦪 silver shellfish
    Thin PR readiness signal; proof, validation, or implementation needs work.