Connect your repository

Without a repository connected, Novix can classify and reply. With one it reads the files it suspects, drafts a patch against code it has actually opened, builds and tests that patch, and opens a pull request.

How many repositories

Connect it under Integrations, on the Codebase tab. A GitHub connection watches up to twenty repositories. GitLab and Bitbucket are one project each today.

Which repository a task goes to

Exactly one, chosen at the start of the run and used by every stage after it: the files it reads, the patch, the sandbox build, the pull request.

• The repository the report came from, when it came from one.
• The repository the report names, when it names exactly one.
• The default you set, otherwise.

Routing declines rather than guesses. A report naming two watched repositories takes the default, so set one you would be happy to be wrong in.

What Novix writes

Reading is read only and budgeted. The only things Novix ever writes to your repository are a branch and a pull request, and at most one repair commit to that same branch when your own CI goes red on it. It never merges, closes, approves or reopens anything.

Teach it your conventions

Put a .novix/guidance.md in the repository and it rides in the prompt for the stages that write. Novix also reads the conventions file your repository may already keep for other coding agents, so a team that has one is covered on its first task with no setup. It is read from the default branch only, so getting text in front of the engine takes the same merge any other change does.