Use cases

Failed Builds on Main, Triaged Automatically

When CI fails, an agent reads the failure, finds the likely cause, and opens a fix when the cause is clear. When it isn't, it reports what it found.

A Failed Build Can Block Merges

A failed build on main can block merges until someone reads the log and works out which change broke it. Most of that time goes to the same steps: find the failing job, read the error, compare it with recent commits.

An Agent Reads the Failure and Proposes the Fix

Use a CI failure event to start an agent. Ask it to run the relevant checks in its session workspace, investigate the likely cause, and propose a fix as a pull request. If it cannot establish the cause, ask it to report the evidence and remaining questions. Review any fix before merging.

Build #2291, npm test

test/users/serialize.test.ts

✕ TypeError: user.profile is undefined

src/users/serialize.ts

- id: user.profile.id,

+ id: user.profile?.id ?? user.id,

Fix opened, checks green

What Teams Report

9.4x

growth in weekly requests across Uber's agent tools, February to August 2026

Uber runs managed agents that self-heal CI failures, with human review or escalation, alongside code review and alert triage.

Uber's software factory post

Common Questions

How does Felan know a build failed?

Send the failure details from your CI system to Felan's authenticated team webhook endpoint. An active automation starts the agent when its provider, event type, and filters match.

Does the agent merge its own fix?

Keep merging under human control. Request a pull request and restrict the agent's permissions so a person must approve the fix.

What if the cause isn't clear?

Ask it to report the failing step, the evidence, and possible causes rather than make an unsupported change.

Which models can it use?

Any major provider, plus local and private models. Bring your own keys or subscription, and there's no markup on tokens.

Can it run on our own infrastructure?

Yes. Use Felan's managed cloud, or run Felan on your own infrastructure with the Enterprise plan.

Related: Webhook events docs, Flaky test cleanup, First-pass code review.

Keep Your Attention for the Hard Problems

Start with one repo and one recurring task.