Feature Request: Conversational Replies with BugBot for Context Clarification

Ideas Feature Requests
,
1

Feature request for product/service

BugBot

Describe the request

Summary

Allow developers to have back-and-forth conversations with BugBot by replying directly to its comments on a PR. BugBot should be able to respond, clarify its reasoning, accept corrections, and update its assessment based on developer input.

Problem

Right now, BugBot operates in a one-way, fire-and-forget fashion. It posts a comment with a bug report and that’s the end of the interaction. This causes real pain in practice:

  • BugBot goes off the rails — it sometimes misidentifies the intent of a code change, and there’s no way to course-correct it mid-review without dismissing the comment entirely
  • Insufficient context in its reports — BugBot’s explanation may be vague or missing the “why”, and there’s no way to ask it to elaborate
  • No iterative refinement — if BugBot flags something that is partially correct but missing nuance, there is no way to have it re-examine with additional context
  • Developer frustration — being forced to work around a static, non-interactive bot creates friction and erodes trust in its output

Proposed Solution

Make BugBot conversational by supporting threaded replies on its PR comments:

  1. Reply to BugBot inline — Developers (and especially team members) can reply directly to a BugBot comment on a PR, just like they would reply to a colleague’s review comment
  2. BugBot reads and responds — BugBot processes the reply with full context of the original comment + thread, and posts a follow-up response
  3. Context injection — Developers can add context BugBot was missing (e.g., “This is intentional because X”) and BugBot should acknowledge it, update its confidence, or retract the issue
  4. Ask for elaboration — Developers can ask BugBot to explain its reasoning in more depth (e.g., “Why do you think this is a bug? What line specifically?”)
  5. Re-evaluation — After a reply, BugBot should be able to revise its verdict: confirm, retract, or escalate the bug with updated reasoning

Example Interaction

BugBot: Possible null dereference on line 42 — user.profile may be undefined.

Dev: This is fine — user.profile is always populated by the auth middleware before this route runs.

BugBot: Got it — if user.profile is guaranteed by upstream middleware, this is not a bug. Marking as resolved. Consider adding a code comment for future reviewers.

Why This Matters

Team members have the best understanding of intended behavior. Giving them a conversational interface with BugBot means:

  • Bugs get properly contextualized instead of dismissed or ignored
  • BugBot improves its on-the-fly accuracy through in-thread feedback
  • The review process feels collaborative rather than adversarial
  • It lays the groundwork for a more powerful, context-aware BugBot over time

Expected Benefits

  • Fewer false positives that drain developer attention
  • Higher trust in BugBot’s output across the team
  • More accurate, context-rich bug reports
  • A natural path toward BugBot learning from team-level domain knowledge

Operating System (if it applies)

MacOS

1 Like
3

Agreed. This is the area where CodeRabbit does better than Bugbot