Bugbot

Bugbot is an automated agent that continuously monitors your pull requests for bugs, security vulnerabilities, and code quality issues. It reviews every PR the moment it opens.

How Bugbot works

Bugbot runs as a Cloud Agent triggered by pull request events. When a PR is opened or updated:

  1. It reads the diff — Bugbot reads only the changed lines, not the entire codebase.
  2. It reads surrounding context — For each changed function, Bugbot reads the full file to understand the changes in context.
  3. It identifies issues — Bugbot looks for logic errors, null pointer exceptions, race conditions, missing error handling, and security issues.
  4. It posts inline comments — Issues are posted as inline GitHub review comments with the file, line, and a clear explanation.
  5. It writes a review summary — A top-level summary lists all issues by severity.

Setting up Bugbot

Bugbot is enabled per-repository:

  1. Go to Settings → Cloud Agents → Bugbot.
  2. Select the repositories where you want Bugbot enabled.
  3. Configure severity thresholds and notification preferences.
  4. Click Save. Bugbot activates on the next PR.

Bugbot requires your GitHub/GitLab integration to be connected and Cloud Agents to be set up for the repository.

Configuring Bugbot

Create a .vyre/bugbot.yaml file in your repository to customize behavior:

yaml
# .vyre/bugbot.yaml
bugbot:
  enabled: true
  
  severity_threshold: medium  # low, medium, high, critical
  
  checks:
    security: true
    logic_errors: true
    missing_error_handling: true
    code_quality: true
    test_coverage: false  # Enable if you want coverage warnings
  
  ignore_paths:
    - "**/*.test.ts"
    - "**/*.spec.ts"
    - "docs/**"
  
  auto_request_changes: false  # Set true to auto-reject PRs with critical issues

Triaging findings

Bugbot comments include triage buttons directly in the GitHub comment:

  • Fix with Agent — Launch a cloud agent to fix the issue and push a commit.
  • Mark as False Positive — Dismiss the finding and add it to Bugbot's ignore list for this repo.
  • Create Issue — Convert the finding into a GitHub issue for later resolution.
Teaching Bugbot about your codebase

Add context to your Bugbot configuration to help it understand your patterns:

yaml
context:
  - "We use `Result<T, E>` types — don't flag missing try/catch for functions returning Result"
  - "Mock functions in tests are intentionally simplified — don't flag missing error handling in test files"
Viewing Bugbot history

Go to Settings → Cloud Agents → Bugbot → History to see all findings across all PRs, filterable by repository, author, severity, and date.