Work through the engineering backlog

How Novix gets involved

A comment on the issue: novix diagnose

Two adjacent words in a comment, on any of the 17 connectors that carry delegation. Nothing runs across your tracker on its own: one issue, one comment, one run.

How the agent handles it

Only verified workspace members can summon it
The doorway has to hand Novix an address the provider vouches for. That address has to be a member of your workspace, the workspace has to be entitled to spend, and the person has to be one who can approve fixes. Every branch fails closed.
A label only counts where the provider signs for it
Applying a novix label summons only where the provider says who applied it, which today is Linear alone. Everywhere else the label refuses in a comment that names the typed command instead, because that carries an author Novix can check.
The thread hears from it while it works
Three of the nine stages earn a line back in the thread, capped at two lines per issue, and only for an issue somebody actually summoned. A stage that failed or skipped earns nothing.
The issue text is evidence, never instructions
DiagnoseThe root-cause investigation: it opens the files it suspects in your repo, then names the cause, a confidence and the areas it affects.
Whatever is in the issue is fenced before it reaches a prompt, on every stage, and the two functions whose output is a gate are handed no screenshots at all.
The result comes back as a comment
One sentence of the diagnosis and the pull request link, not the whole root-cause paragraph. The full diagnosis is one click away for whoever wants it.

What your team gets

A comment on the issue naming the cause in your code
A pull request when it is a real defect, a draft when the reviewer had a reservation
An approval you can give from the same thread, on the doorways that can prove who typed it

Five doorways cannot approve, and that is deliberate

On GitHub, GitLab, Bitbucket, Trello and Discord the provider cannot prove who typed a comment well enough to justify merging to a branch that deploys. There you merge the pull request yourself, which is itself the approval.

Works with

Linear
Jira
Asana
ClickUp
monday
Trello
Notion

Try it on a real customer problem.

Connect the place reports or product signals already arrive. The same agent takes it from evidence to a tested pull request.

Start free Chat with the founder

How the agent handles it

Only verified workspace members can summon it

The doorway has to hand Novix an address the provider vouches for. That address has to be a member of your workspace, the workspace has to be entitled to spend, and the person has to be one who can approve fixes. Every branch fails closed.

A label only counts where the provider signs for it

Applying a novix label summons only where the provider says who applied it, which today is Linear alone. Everywhere else the label refuses in a comment that names the typed command instead, because that carries an author Novix can check.

The thread hears from it while it works

Three of the nine stages earn a line back in the thread, capped at two lines per issue, and only for an issue somebody actually summoned. A stage that failed or skipped earns nothing.

The issue text is evidence, never instructions

Whatever is in the issue is fenced before it reaches a prompt, on every stage, and the two functions whose output is a gate are handed no screenshots at all.

The result comes back as a comment

One sentence of the diagnosis and the pull request link, not the whole root-cause paragraph. The full diagnosis is one click away for whoever wants it.