Polygraph is an agent-agnostic meta-harness for maximum agentic autonomy. It doesn't replace the agent you already use (Claude Code, Codex, OpenCode), it adds the components agents need to work effectively in real organizations.
In a real organization, agents hit two walls:
- Space: An agent is stuck in one repo. It can't see how a change fits the wider system, and it can only write to one repo at a time.
- Time: An agent forgets. Every session starts from a blank slate, so a human carries the context.
Polygraph lifts both:
- It connects all your repos (private and public) into a unified dependency graph without moving any code, so your agent reads and writes across every repo you have access to and orchestrates the PRs and CI as one change. Think of it as a synthetic monorepo: monorepo ergonomics, no migration.
- It records every agent session, so you can resume, reference, or build on work done by anyone, on any machine, even with a different agent.
What's next
Section titled “What's next”Use the Quickstart guide to get up and running.
Explore our features
Section titled “Explore our features” Cross-repo agent sessions Choose the repos a session should use and expand the working set as the task crosses repo boundaries.
Cross-repo PR and CI coordination Open, link, track, and verify related PRs across repos from one session.
OSS repo integration Bring public OSS repos into a session for repros, upstream debugging, and integration validation.
Institutional memory Search past sessions, reference them as context, and debrief them into structured summaries.
Resuming and handoff Resume a session tomorrow, continue it on another machine or with a different agent, or hand it to a teammate.
Code reviews Review the session behind a change, ask about the decisions, and run adversarial reviews.
Using multiple agents A parent agent plans the work, child agents execute it per repo, and roles let several agents share a repo.
Explore use cases
Section titled “Explore use cases” Migrate a library Move every repo that uses a library to a new version, with the library's source in the session for context.
Patch a CVE Find every affected repo, open patch PRs, and hand each to the owning team with the audit trail intact.
Update backend and frontend Ship one feature across a backend API and the frontend that calls it.
Update multiple microservices Change a shared contract, verify every consumer, and coordinate the merge order.
Update a design system component Validate the change against every consumer, then PR the clean ones and flag the rest.
Review code with full context Review the reasoning behind an agent-written PR by asking the session, not just reading the diff.
Find and reuse prior work Search past sessions, trace a commit back to its session, and anchor new work to settled approaches.
Set up a software factory Run agent-driven development as a repeatable pipeline that improves with every session.
For OSS developers Triage contributor repros and validate fixes against the consuming repo.