Summon Novix where you work

Seventeen connectors carry delegation, which means you can summon Novix from them and see the answer come back in the same place. Slack is a doorway by its own route, and email is a doorway twice over.

The command

novix diagnose

Write it in a comment on the issue, ticket or page that describes the bug. It works on every doorway whose provider will tell Novix who wrote the comment.

On the nine issue trackers and Notion, the bare word novix is enough: "novix can you look at the timeout in the second block" reads as a request. Naming Novix in passing is not a summons, and a cheap triage gate decides which is which and fails closed.

On the six help desks the exact two words are required, because those threads carry conversations with your customers, who say the word for reasons that have nothing to do with Novix.

Tag @Novix, or name Novix

Slack, Discord and Linear are the only doorways where Novix has an identity of its own, so they are the only ones where you can tag it. Everywhere else Novix acts as the account that connected the integration, so there is no @Novix to tag and you write its name instead. The outcome Novix posts always tells you which one applies there.

A label, a tag or a property

A novix label summons on Linear, and so does naming Novix anywhere in the issue’s own description, whether that is a brand new issue or one you edit later. On Jira, Asana, ClickUp and monday the label works when the provider will tell Novix who applied it, and refuses in a comment naming the command above when it will not. Trello can never answer that question, so a label there always refuses.

Notion has the same gesture in its own grammar: name a checkbox or a status option in the integration’s settings, and setting it on a database row is the summons. It stays off until you name one.

In Slack, and in Discord

In Slack, mention Novix in a thread. The thread is the report: the first message and everyone up to your mention come with it, and Novix replies in that thread when it starts and again when it finishes.

In Discord, a channel can be set to take every message, so a support channel needs no summons at all. Threads are always mention only, and every channel starts off.

On a help desk, the command is internal

Novix reads the command from an internal note, never a public reply. Otherwise a customer could start runs, approve a merge or read a diagnosis written for your team.

Who may summon

The provider has to vouch for your identity, but you do not need a separate Novix account or paid seat to start a run. That makes @Novix work for the whole team in Slack, Linear and every other doorway that can prove who asked. Approving or merging a fix still requires the approve fixes permission.

The terminal and MCP

A command-line tool and an MCP server are published on npm under @novix-ai, calling the same public task API. Neither has made an authenticated call against production yet, so treat them as code rather than a proven doorway.