PROJECT 02← All work

AI-assisted developer tooling

PatchPilot X

From engineering alert to evidence-backed patch

ROLE

Agent workflow design, backend and interface engineering

YEAR

2026

STATUS

Open-source project

OVERVIEW

A remediation workflow that proves impact, creates a failing reproduction test, localizes the root cause, evaluates candidate patches, verifies the result in a sandbox, and produces a pull-request artifact.

01

Problem

Automated remediation is untrustworthy when a language model can claim that a patch works without reproducible evidence.

02

Constraints

The workflow had to degrade safely when optional integrations fail, separate reporting from verification, and work without granting repository write credentials.

03

Architecture

A FastAPI orchestration layer manages structured tracing, candidate patch evaluation, sandbox execution, and optional GitHub communication around a React operator view.

04

Key decisions

A failing reproduction test is created before patch generation. Candidate patches compete against the same deterministic checks, and the LLM never decides whether those tests passed.

05

Walkthrough

Alert → impact proof → failing reproduction test → localization → patch tournament → sandbox verification → PR artifact → team communication → memory update → trace.

06

Security, safety & reliability

Sandbox boundaries, credential-gated writes, structured traces, and safe integration fallbacks constrain what automated components can change.

07

Testing & evaluation

Pytest and sandbox execution supply the evidence. A patch only advances when the deterministic reproduction and regression checks say it can.

08

Result

The project turns remediation into an inspectable evidence chain rather than a generated patch plus an unsupported success claim.

09

Limitations

Repository behavior, sandbox parity, and optional integrations still vary by environment. Real pull-request creation requires explicit credentials and configuration.

10

Lessons

Agentic workflows become safer when every probabilistic step produces an artifact that a deterministic step can check.

PROJECT-LOCAL PROOF

Tests and deterministic verification decide whether remediation succeeds

Local and Docker sandbox modes are supported

Real pull-request creation is optional and credential-gated

NEXT PROJECT / 03

Zulip MCP