BUILT WITH LANGGRAPH · VERIFIED IN ISOLATION

Dependencies
break.
Keep moving.

An AI agent that turns breaking upgrades into reviewable repairs. Reproduce the failure. Fix the code. Prove it works.

Open repair workspace ↗Explore the architecture ↓
+ Python + Node.js+ Bounded agent loops+ Human approval
✦ REPAIR ENGINE 01 / AGENT GRAPH
↯
Breaking changeClient(app=…) removed
dr↗REASON · REPAIR · VERIFY
✓
Verification passed2 / 2 tests · recorded run
WORKFLOW ILLUSTRATION ↗
THE AGENT DOES THE WORK.
THE EVIDENCE MAKES THE CASE.
01 Reproduce
→
02 Repair
→
03 Verify
→
04 Review
01 / SEE THE WORK

A tiny API change.
A very real failure.

HTTPX removed a constructor argument.
Follow the agent from failing test to verified patch.

● RECORDED DEVELOPMENT VALIDATIONHTTPX 0.27.2 → 0.28.1

Interactive replay of a local development fixture. This does not execute a new repair.

FAILURE REPRODUCED1 / 2 passing

The upgrade breaks a test.

The baseline passes both tests. Upgrading HTTPX exposes an incompatible constructor argument.

● ● ●pytest · isolated container
E   TypeError: Client.__init__() got an
    unexpected keyword argument 'app'

FAILED  test_wsgi_response
PASSED  test_no_provider_credentials

1 failed, 1 passed
BASELINE2 / 2 ✓
AFTER UPGRADE1 / 2 ↯
AFTER REPAIR2 / 2 ✓
Same tests. New dependency version. A reproducible failure.

Local Python development fixture · Gemini 3.1 Pro Preview · tests and installed packages unchanged · awaiting human approval. This is recorded development validation, not an upstream HTTPX repository repair.

02 / MORE THAN A PROMPT

A graph with
checks at every turn.

Explicit state. Bounded retries. Isolated execution.
Every proposed repair has to earn its review.

LANGGRAPH / STATEFUL ORCHESTRATIONArchitecture view
↳IntakeInspect repository
Validate dependency
→
⌁ReproduceBaseline tests
Upgrade & compare
→
✳Repair agentInvestigate · diagnose
Generate focused patch
→
✓VerifyRun protected tests
Check integrity
→
◇Human reviewInspect evidence
Approve or reject
↳ Failed verification returns feedback to the agent. Retry limits keep execution bounded. ↰
⌘
01 / CONNECT

Your repository.
A controlled workflow.

GitHub OAuth and MCP inspection connect repository context to Python and Node.js dependency workflows.

⬡
02 / CONTAIN

Execution has
boundaries.

Docker isolation, offline tests, resource limits, and protected tests constrain what a repair can change.

↗
03 / EXPLAIN

A patch with
its proof attached.

Before-and-after results, the proposed diff, and an execution trace help a reviewer make the final decision.

03 / BUILT TO BE EXPLAINED

Not just “the AI fixed it.”
Here’s how. Here’s the proof.

Explore the repair above, then go deeper into the engineering decisions.

Read the engineering brief ↗Replay the repair ↺
◈

About this deploymentThis Azure site is the interactive project showcase. Live repository repair uses a separately hosted API and isolated worker. Open the workspace to sign in and check backend readiness.