Polygraph

Session memory is awesome, especially if it can be configured to be used in a safe manner for OSS maintainers as it will make reproductions a little easier.Curious if access control has been considered for large enterprise organisations where contributors to some repos may not have access to other repos that are downstream of changes they want to make. It currently feels like it’ll work wonders for contributors and orgs that allow access to all repos, but there seems to be unknowns right now around how this would work for orgs with stricter access policies.

The session memory piece is the hard part - most AI coding tools treat every conversation as stateless, which means re-explaining the same codebase context over and over. The cross-repo visibility is interesting because naively including every repo would blow the context window, so curious how you're handling that tradeoff. Is it doing dependency graph traversal to selectively pull in relevant context, or more of a semantic similarity search over chunked code? And does the session memory persist across different agent frameworks (Claude Code, Cursor, etc.) or is it scoped to one at a time?

I've been using Polygraph daily for the last few months, can genuinely say it's been a big upgrade from my old way of working. It's so easy to start working on a change and get everything I need set up immediately, so I can start working on the actual problem right away. Especially when I need context from a coworker's session or need to make a PR to another repo for some config related to a change I'm making, Polygraph makes it so easy I don't need to think about it. Amazing work team 🤩

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?

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.

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.

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! 🚀

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!