Use cases
Start with the customer problem.
Someone summons Novix, or a signal does. Both end in a tested pull request.
Customer-reported problems
A customer reports a problem. Novix brings their context, the code and the fix into one run.
- Turn support tickets into tested fixesA customer reports a product problem in the help desk your team already uses.A new ticket in your connected help desk.Zendesk · Intercom · Freshdesk · Help Scout · Front · Gorgias
- Investigate a bug report with missing detailsA customer reports a real problem but leaves out the detail needed to investigate it.The original customer thread.Zendesk · Intercom · Slack · Linear
- Close the loop with the customerThe engineering work is complete, but the customer still needs a clear answer.Every completed Novix run.Zendesk · Intercom · Help Scout · Front
Engineering
Summon the same agent for backlog work, unfamiliar code and incidents that arrive after hours.
- Work through the engineering backlogAn issue has been waiting because nobody has had time to investigate it properly.A comment on the issue: novix diagnoseLinear · Jira · Asana · ClickUp · monday · Trello · Notion
- Fix product errors before customers report themMonitoring sees customers hitting an error before a support ticket exists.A monitoring signal auto-summons Novix.Sentry · Datadog · Rollbar · PagerDuty · Statuspage
- Make safe changes in unfamiliar codeThe problem sits in a service nobody on the current team knows well.Any report on that repository.GitHub · GitLab · Bitbucket
- Investigate incidents while your team is offlineA customer report or product signal arrives while the team is asleep.A customer report or an auto-summon.Slack · Discord · Forwarded email · Sentry
- Recognize a problem you fixed beforeA customer reports a failure that resembles an earlier incident.Every run, at the memory stage.
Your stack and setup
Use the intake, repositories and inference account your team already has.
- Turn email, forms and chat into tested fixesCustomer problems arrive by email, a shared channel or your product instead of a help desk.A forwarded email, a widget message or a form.Chat widget · Report form · Forwarded email
- Route every report to the right repositoryA customer reports one problem, but your product spans several services.Any report, routed on the way in.GitHub · GitLab · Bitbucket
- Run Novix on your own inference accountYour security or procurement team wants model usage billed through your provider account.Inference settings on the Pro plan.Anthropic · Kimi · OpenAI · Google Gemini · DeepSeek · OpenRouter
What it is not for
Four jobs Novix deliberately leaves to other products or to a person.
Deciding product direction
Novix tells a bug from a change and says which it decided. A change still gets a diagnosis and a drafted patch, in a draft pull request, because what to build is your call.
Repositories that need an unsupported toolchain
The verification container ships git, node and python. A repo that needs another toolchain is told exactly that instead of handed a verdict, and no fix is reported as passing a build that did not run.
Replacing your issue tracker
Novix is not an issue tracker and never asks you to move anything into it. It reads Linear, Jira and your help desk, and writes back to them.
Sending customer messages without review
The AI is pointed at your engineers. Every customer reply is drafted for a person to read and send, and nothing goes out on its own.
Have a customer problem that looks different?
Show us where it arrives and what context your team has. We will tell you plainly whether Novix fits.