Alchemist: Self-Healing

Alchemist can watch your running app’s logs and automatically open a fix-ticket when new problems show up — so a regression doesn’t sit unnoticed until a user reports it. You configure this on a project’s settings page under Self-healing.

There are two independent sweeps, each toggled and scheduled on its own:

Error sweep — scans your app’s error logs and, when new error signatures appear, opens a single batched fix-ticket describing them. Default cadence: every 30 minutes.
Behavior sweep — reviews warnings, errors, and breadcrumbs across a window and opens a findings ticket for issues worth a closer look (not just hard crashes). Default cadence: weekly.

Configuring cadence

Each sweep has an Every dropdown. Leaving a sweep untouched runs it at the default cadence shown next to it. You can make a sweep more or less frequent, or turn it off entirely with its toggle. Sweep cadences are clamped to a range of every 30 minutes at most and every 30 days at least.

Approval and cost cap

Before a fix runs controls whether a sweep’s fix starts on its own:

Ask me first (default): each fix waits for your approval in the project’s Approvals tab. A fix with no decision expires after 48 hours.
Run automatically: the fix starts as soon as the sweep finds something.

Per-fix cap sets the most one fix can spend (default $35). A fix that would cost more stops and asks for more budget.

What you get

When a sweep finds something new (and, in Ask me first mode, you approve it), it opens a normal ticket in your project — so the fix flows through the same agent pipeline as any other work, and you can follow it in the Jobs view. Repeat occurrences of an error the platform has already filed are de-duplicated, so you won’t get a fresh ticket every sweep for the same known issue.

Notes

Sweeps only act on new signatures since the last run; a steady, already- ticketed error won’t re-open tickets.
Turning a sweep off stops new tickets from that sweep immediately; it does not close tickets already opened.