Labels

• bug

  Something isn't working
• claude
• codex

  Routes the issue to the Codex provider for execution.
• dependencies

  Pull requests that update a dependency file
• documentation

  Improvements or additions to documentation
• duplicate

  This issue or pull request already exists
• enhancement

  New feature or request
• gemini

  Routes the issue to the Gemini provider for execution.
• go

  Pull requests that update go code
• good first issue

  Good for newcomers
• help wanted

  Extra attention is needed
• invalid

  This doesn't seem right
• question

  Further information is requested
• resume
• vigilante:automerge
• vigilante:awaiting-user-validation

  Changes are ready for product or operator validation before the issue is considered done.
• vigilante:blocked

  Execution cannot continue until a blocker is resolved.
• vigilante:done

  Vigilante completed its work on the issue and no further automation is expected.
• vigilante:flagged-security-review

  Vigilante's deterministic package hardening process found issues requiring human review.
• vigilante:iterating

  An assignee-requested follow-up implementation iteration is actively in progress.
• vigilante:needs-git-fix

  Execution is blocked by repository or git state that requires human repair.
• vigilante:needs-human-input

  The agent is waiting on product, operator, or repository-owner guidance.
• vigilante:needs-provider-fix

  Execution is blocked by provider auth, quota, or runtime setup issues.
• vigilante:needs-review

  A human should review the implementation output before Vigilante continues or closes the loop.
• vigilante:queued

  The issue is eligible for dispatch and waiting for a worker slot.
• vigilante:ready-for-review

  Implementation is complete enough for a human to review the resulting PR or branch.
• vigilante:recovering

  An automatic stale-session recovery attempt is actively rebuilding local execution state.
• vigilante:resume

  Requests that Vigilante resume a blocked session.
• vigilante:running

  A coding-agent session is currently executing for the issue.
• wontfix

  This will not be worked on