Self-Healing Production Agent

A self-healing pipeline detects post-deploy regressions, triages whether the deploy caused them, and dispatches an agent to open a fix PR for human review.

The loop

The self-healing loop automates the first three steps of the incident cycle and keeps human judgment for the merge gate alone. The classic cycle — detect, ticket, triage, fix, review — needs a person at every hand-off.

graph TD
    A[Deploy] --> B[Run eval suite / functional tests]
    B --> C{Regression detected?}
    C -->|No| D[Done]
    C -->|Yes| E[Causality triage agent]
    E --> F{New or pre-existing?}
    F -->|Pre-existing| G[Log and skip]
    F -->|New — caused by deploy| K{Fix attempts exceeded?}
    K -->|Yes — circuit breaker| L[Escalate to human ticket]
    K -->|No| H[Fix agent]
    H --> I[Open fix PR]
    I --> J[Human review & merge]

LangChain applied this to their GTM Agent: after every deploy, the system compares eval scores before and after the deploy, triages causality, and opens a fix PR (LangChain: How My Agents Self-Heal in Production, April 2026).

Four components

1. Regression detection

Compare a fixed eval suite or functional test results before and after each deploy. A score drop or new failure triggers the loop. Use the same deterministic graders used for harness hill-climbing — test suite pass/fail and schema checks are more reliable than LLM-as-judge for repeated automated runs (Anthropic: Demystifying evals for AI agents).

Trigger condition: post-deploy score falls below a threshold or one or more test cases that previously passed now fail.

2. Causality triage

The current deploy does not cause every regression. A triage agent — the attribution step in LangChain's GTM Agent loop — compares the failure against pre-deploy baselines to find the cause:

Outcome	Action
Regression present before deploy	Log as pre-existing; skip fix dispatch
Regression appeared after deploy	Attribute to current change; dispatch fix agent
Ambiguous	Escalate to human; do not dispatch

The causal diff — the changes in the deploy that correlate with the failure — becomes part of the fix agent's input. Without triage, every test flake generates a fix PR, burning tokens and review capacity.

3. Fix agent dispatch

The fix agent receives three inputs: the failing test, the causal diff, and a fix-PR instruction. It writes the minimal change to make the test pass without broadening scope, then opens a PR against the main branch — leaving main untouched until human merge, consistent with rollback-first design.

Scope constraints: - Fix is limited to the failing test's coverage area - No refactoring unless directly required by the fix - PR description includes the triggering eval result and the causal diff for reviewer context

4. Circuit breaker

Repeated fix attempts on the same regression — each failing — indicate the agent cannot self-resolve the issue. A circuit breaker stops dispatch after N consecutive failed attempts for a given regression identifier and escalates to a human ticket instead.

Without this gate, the loop generates unbounded fix PRs on an unfixable regression, consuming tokens and polluting the PR queue. The same principle underlies per-tool circuit breakers; here it applies at the fix-dispatch level.

Human gate

Fix PRs go to human review; no auto-merge without approval. This is a structural requirement, not a configuration option. The fix agent operates on a branch, leaving main unchanged until a human confirms — consistent with rollback-first design.

Auto-merge without review converts a reliability pattern into a liability: an agent with write access to production and no approval step.

Scope boundaries

This pattern handles post-deploy regression detection and remediation. It does not:

• Improve overall agent quality offline (see Agentic Flywheel)
• Tune harness configuration against an eval suite (see Harness Hill-Climbing)
• Catch regressions introduced by the fix PR itself — the same pipeline re-runs after the fix PR merges

Example

A Python service uses pytest as its eval suite. A GitHub Actions workflow triggers on every deploy:

# .github/workflows/self-heal.yml
on:
  deployment_status:
    types: [success]

jobs:
  regression-check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Run post-deploy eval suite
        id: eval
        run: |
          pytest tests/evals/ --json-report --json-report-file=results.json
          python scripts/compare_baselines.py results.json baseline.json > diff.json
      - name: Dispatch fix agent if regression detected
        if: steps.eval.outputs.regression == 'true'
        run: |
          python scripts/triage_and_dispatch.py \
            --diff diff.json \
            --causal-commit ${{ github.sha }} \
            --fix-agent claude-code \
            --circuit-breaker-key "${{ github.repository }}-${{ github.sha }}"

compare_baselines.py compares pass/fail per test case. triage_and_dispatch.py checks whether each newly failing test passed in the pre-deploy baseline; if so, it attributes the regression to the current commit and calls the fix agent with three inputs: the failing test path, the git diff, and a PR-creation instruction. It increments a counter keyed by (repo, failing_test) in a shared store; once the counter hits N, it opens a human escalation ticket instead of dispatching.

When this backfires

The pattern adds overhead that only pays off under specific conditions:

• Low deploy frequency: teams shipping once a week or less rarely need automated causality triage — the deploy-to-failure gap is wide enough for manual triage to stay fast.
• No stable eval suite: the loop needs a fixed set of deterministic graders to compare scores before and after a deploy — the same stable suite harness hill-climbing tunes against. If the eval suite itself changes between deploys, the causal diff becomes unreliable and triage produces false positives.
• Fix agent exceeds the scope constraint: if the fix agent regularly writes changes outside the failing test's coverage area — coding-agent scope expansion — human reviewers face a growing review burden that can exceed the time saved by automated dispatch. This usually signals that the regression is architectural, not surgical.
• High flake rate in the test suite: intermittent failures that no deploy caused trigger the triage agent repeatedly, exhaust the circuit breaker budget, and escalate noise to human tickets — the opposite of what the pattern promises.

Key Takeaways

• Trigger on deploy events, not scheduled runs — the loop is reactive, not periodic
• Causality triage is mandatory; without it, pre-existing failures generate spurious fix PRs
• The fix agent's scope must be bounded to the failing test — broad fixes increase review burden and risk
• Circuit-break after repeated failures on the same regression; unbounded dispatch wastes tokens and review capacity
• Human review at merge is non-negotiable — auto-merge without approval is not a variant of this pattern

Related

• Agentic Flywheel — offline loop that improves the harness itself, not individual regressions
• Harness Hill-Climbing — eval-driven iterative tuning of agent harness configuration
• Agent Circuit Breaker — per-tool failure tracking; the same stopping concept applied at loop level here
• Rollback-First Design — every fix runs on a branch; main is only updated via human-approved merge
• Exception Handling and Recovery Patterns — broader taxonomy of agent failure modes
• Evaluator-Optimizer Pattern — two-role LLM loop for iterative output refinement

Adopted — practitioner-sourced, corroborated Last reviewed: 2026-06-12