Polygraph has access to all public repositories on GitHub. It knows what's in them, how they relate to each other.
And it can add public open source repos to a session alongside the repos you own. That makes OSS repros, upstream libraries, and downstream consumers part of the same working context.
When to use it
Section titled “When to use it”Use OSS repo integration when:
- A bug report includes a public reproduction repo
- Your code depends on a public upstream project
- You need to validate an unpublished fix against a public consumer
- You want the agent to inspect OSS code without treating it as a repo you own
Add an OSS repo to a session
Section titled “Add an OSS repo to a session”Paste the repo URL into the agent and ask it to add the repo to the session.
Please add @opentui/core to this sesssion and check if I use the api correctly.For a full maintainer workflow, see For OSS developers.
Validate package changes
Section titled “Validate package changes”For publisher-consumer validation, the agent can use pack_and_copy to pack a changed package and install the tarball into a consumer repo inside the session.
That gives you an end-to-end loop for OSS repros: reproduce the bug, change the publisher, install the unpublished package into the repro, rerun the failing command, and open the PR in the repo you own.
Keep PR direction clear
Section titled “Keep PR direction clear”External OSS repos can be useful working context without becoming PR targets. For example, a contributor's repro can stay read-only from a PR perspective while Polygraph opens the fix against your library.