A sandbox tested PR,from a Sentry log.

An alert fires

Novix reads the exception out of the monitoring you connected, so a run can start with nobody awake to report it. The alert is the summons, and everything below is what happens next.

PostHog waits until a threshold of real users has hit the same exception, so one stale tab does not open a task.

All of these match

Filters narrow which alerts may auto-summon Novix: a route can match on the environment, on text in the alert, or on its level. A repeat of the same alert inside a window you choose is still filed as a task but is not diagnosed a second time.

An alert matching no auto-summon is still diagnosed. A filter decides where the answer is published, never whether Novix looks.

Quiet hours

Held, not dropped. The window runs in the time zone you chose. When it ends, each alert is announced to its destination and only then diagnosed, so nothing is lost and nobody is woken.

Only defects continue

Checked before and after diagnosis. Recoveries, acknowledgements, and test pages stop; questions stay for a person.

Always on, and not a setting.

Novix diagnoses it

The same agent loop a person summons. It reads the files it suspects in your repository, names a root cause with a confidence, drafts a patch, then runs your own build and tests against it in an isolated sandbox.

A pull request opens

A pull request always opens. What the review decides is whether it arrives ready for review or as a draft carrying the reason, and nothing merges without a person.

Always on, and not a setting.

Novix posts the answer

The result goes wherever you chose: a Slack thread, a Discord message, a Linear issue, a Notion page or an email.

On Slack you can reply in the thread to approve the fix, without opening Novix.