Launching today
AI coding agents are limited to how autonomously they can work because they have no model of the codebase as a whole. Polygraph is a meta-harness that gives agents what they're missing: Visibility across every repo boundary and memory that survives the session. Connect all your repos, private and public, into a unified dependency graph without moving any code. Resume, reference or build on any session created by any developer, on another machine, even on different agents.
Polygraph
Our founders, Jeff Cross and Victor Savkin, have been building monorepo tooling for over a decade. In the last few years we've noticed that the ergonomics of monorepos have been especially great with AI agents. All your code visible in one place, allowing you or your agents to quickly see the full context it needs to make decisions that won't break your CI when it comes time to merge.
We wanted to bring this to the whole developer tooling community because we know even if some teams use monorepos, it's not realistic to have an entire org on one (unless you're Google.) It started by building a dependency graph - a sort of synthetic monorepo - and then we had to tackle agentic amnesia. Agents are great, but having to re-explain yourself or losing context sucks. Like a game of telephone, it's never the same as being able to stay in session.
We built Polygraph for:
Individual devs: If you're deep in a feature that touches 3 repos, Polygraph will set up all 3 in a single session, manage CI across them, and keep a record of everything your agent did. A week later if you need to fix a bug or go on PTO and want to hand it off to a teammate, they can continue it on their machine without any loss.
Teams across services: If a change to a shared library touches 5 downstream repos, Polygraph lets your agent validate that change across all 5 before a single PR is opened. It then opens and manages the cross-repo PRs and CI together, so the whole change moves as one unit.
Thanks for checking out our new product - we'd love to get your feedback!
This is a really interesting idea. Cross-repo context is one of the biggest limitations I've run into with AI coding agents.
I'm curious: how do you keep the dependency graph accurate as repositories evolve independently? Is it updated continuously from Git changes, or rebuilt on demand before an agent starts working?
Congrats on the launch! 🚀
Polygraph
@prashant_patil14 thanks for the feedback and checking out Polygraph!
The repository graph is updated once a day or on demand when users request it since inter-repo dependencies aren't something that changes super often, it's more of a slow evolution.
The graph of sessions and code changes is updated more regularly, whenever new git changes come in or PRs are created :)
Hope that helps, happy to chat more about it
love this. agent amnesia is easily one of biggest pain right now when working across multiple repos.
quick question, what happens if another developer pushes new code to a repo while my AI agent is still working on it? does the agent realize the code changed, or do I have to restart the session? great launch guys.
Polygraph
@wilder_dev thanks for the kind words, Erik!
Polygraph doesn't ship anything here beyond what git already has. So you can make a PR and that might just be unaffected by the new changes.
What polygraph does have though is CI monitoring and skills for helping your agent fix CI across all the different PRs across repos. So if there's a merge conflict, polygraph can help you figure it out and make any further updates that are required after resolving the conflict.
@max_kless2 got it, that makes perfect sense. thanks for clarifying!
Polygraph
@wilder_dev you got it! Let me know if you have any other questions and try it out!! :P
https://app.trypolygraph.com/
Cross repo visibility plus resumable sessions is a real unlock. A session snapshot carries state and code from several private repos, and another developer can pick it up on their own machine. Does the snapshot respect per repo permissions, so resuming a session never hands someone context from a repo they aren't allowed to see?
Polygraph
@angelika_dev yes! You can only interact with sessions for which you have access to all the repos.
If all the repos are open-source, you can generate a share link so external ppl can have a look at your session as well (like for repros in bug reports for example).
If sessions can be resumed by a different developer on a different machine using a different agent, what's actually being preserved, is it raw conversation history, a structured summary, decisions/rationale, or something closer to a full state snapshot? That distinction matters a lot for whether "resuming" actually picks up where the original left off or just gives vague context.
Nx
@ansari_adin it's a full state snapshot including all prompts and responses, sub-agent work, state of the repository(s) but also references to other sessions and their states (like building a hive mind). You can resume the work as if you were running it from the start.