Getting started

What Novix does

Novix reads a bug report from wherever it landed, finds the root cause in your code, and opens a pull request a person approves.

The whole product is one loop: a report comes in, Novix diagnoses it, drafts a fix, a person approves that fix, and every decision sharpens the next run.

report → diagnose → fix → approve → learn

One engine, many doorways

A report can arrive from Slack, Linear, Jira, a help desk, a forwarded email, or one of the other 37 connectors. The approval can happen in the same place. Novix is the engine in the middle, not somewhere you go.

One doorway has nobody behind it. Point your error tracking at Novix and an auto-summon starts the same agent loop with no report and no reporter: your monitoring fires, Novix diagnoses it against your code, and the answer is published where you said.

After setup you should not need to open Novix again: the doorway you already have open is the product.

What the dashboard is for

It has four jobs, and nothing on it exists outside them.

Wire it up. Connect the doorways, pick the repositories, choose the engine settings.
Set policy. What Novix may do on its own, who can approve, which repositories it may patch.
Show evidence. What a run did, what it cost, whether it was any good.
Catch the exceptions. The small set of things that could not be finished in the doorway they arrived from.

The words this documentation uses

Word	Means
task	One unit of work: a report in, a run over it, a pull request out.
doorway	A place you can reach Novix from, and be answered in.
run	One execution of the nine stages against a task. A task can have several.
summon	Asking Novix to start.
approve	A person deciding a drafted fix ships. Merging the pull request is this.
steer	Telling Novix how you would have fixed it, so it drafts again.

Ticket survives in one place only: what a help desk hands over. It becomes a task the moment Novix has it.

What Novix is not

Not an issue tracker. You have Linear or Jira. Novix reads them and writes back to them, and never asks you to move your work.
Not a help desk you have to adopt. Novix has its own intake if you want one, but it is built to sit under the help desk you already run.
Not a bot that answers your customers. The AI is pointed at the engineer. A person sends every customer reply.
Not model agnostic. Novix is built on Claude and tuned for it. You can run it on your own inference account, which changes whose account pays, not which model does the work.
Not an autonomous deployer. Novix opens a pull request at most. A person merges.

NextConnect your first source

One engine, many doorways

After setup you should not need to open Novix again: the doorway you already have open is the product.

What the dashboard is for

It has four jobs, and nothing on it exists outside them.

Wire it up. Connect the doorways, pick the repositories, choose the engine settings.

Set policy. What Novix may do on its own, who can approve, which repositories it may patch.

Show evidence. What a run did, what it cost, whether it was any good.

Catch the exceptions. The small set of things that could not be finished in the doorway they arrived from.

The words this documentation uses

Word	Means
task	One unit of work: a report in, a run over it, a pull request out.
doorway	A place you can reach Novix from, and be answered in.
run	One execution of the nine stages against a task. A task can have several.
summon	Asking Novix to start.
approve	A person deciding a drafted fix ships. Merging the pull request is this.
steer	Telling Novix how you would have fixed it, so it drafts again.

Ticket survives in one place only: what a help desk hands over. It becomes a task the moment Novix has it.

What Novix is not

Not an issue tracker. You have Linear or Jira. Novix reads them and writes back to them, and never asks you to move your work.

Not a help desk you have to adopt. Novix has its own intake if you want one, but it is built to sit under the help desk you already run.

Not a bot that answers your customers. The AI is pointed at the engineer. A person sends every customer reply.

Not model agnostic. Novix is built on Claude and tuned for it. You can run it on your own inference account, which changes whose account pays, not which model does the work.

Not an autonomous deployer. Novix opens a pull request at most. A person merges.