Alchemist: Self-Healing
The platform watches your deployed app's errors and behavior and files fix tickets automatically.
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: every 6 hours.
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 sensible range: no tighter than every few minutes, no looser than once a day.
When a sweep finds something new, 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.
- 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.
Self-healing tickets consume credits like any other ticket. If you're running a tight monthly budget on a client project, start with the error sweep only and leave the behavior sweep off until you've seen a few weeks of normal traffic.
*AVCodex · Your AV expertise. Amplified by AI.*