Hey @shamashel, good question. BugBot currently works within a single repository. It only analyzes the PR diff and the code in that repo. GitHub’s Agentic Workflows and similar tools work differently because they spin up a full agent that can clone and navigate multiple repos. BugBot is more focused on the individual PR context, which is a deliberate tradeoff for speed and reliability.
There’s no cross-repo support on the roadmap right now, but we’ve noted the interest. I also saw a separate feature request here: Multi-Repo BugBot Support. That’s helpful for tracking demand.
If your team wants to push this through official channels, that works too. Your account rep or sales contact can pass it along. The more concrete the use case is, like “we need type consistency checks between repos X and Y”, the easier it is to prioritize.
In the meantime, a CI-based approach, like checking out both repos in a GitHub Action, is probably the most practical way to catch cross-repo issues automatically.