Your agent is not replying in Slack

Work through these in order. The first two cover most cases.

1. Did you mention the agent at the start?

The bot answers a message that begins with a mention, for example @Nairi why did the deploy fail. A mention in the middle of a sentence, or no mention at all, is ignored on purpose so the bot stays quiet in a busy channel.

2. Is the bot in the channel?

Run /invite @Nairi. The bot only sees channels it has been invited to, and a private channel needs that invitation just as a public one does.

3. Is there an hourglass on your message?

⌛ means the task is queued rather than lost. An agent's instance count, from 1 to 10, caps how many tasks run at once, and the rest wait. Raise the instance count, or wait for the current work to finish. Note the concurrent-task limit is 1 on Hobby and 5 on Team.

4. Is a channel bound to the agent you think?

Run /nairi agent to see the current binding, and /nairi agents to see the options. A channel binds to your organisation's first active agent the first time anyone mentions the bot there, which is not always the one you meant. Rebind with /nairi agent=ag_....

5. Is the agent online and does it have a model?

Check the agent in Fleet. An agent with no working LLM integration deploys but cannot answer. If you rotated the provider API key, put the new one in Settings → Integrations.

6. Read the transcript

Every task, including a failed one, appears under Tasks with its full transcript and every tool call. A ❌ reaction means the task failed and the reason is in there. This is the fastest way to tell a model problem from a permissions problem.

Self-hosted agents

A stale heartbeat means nairid cannot reach the backend. Check NAIRI_API_KEY is still valid and that nothing is blocking the WebSocket. "Namespace already locked" means a second instance is running with the same NAIRI_AGENT_ID.

If none of this explains it, email support@nairi.ai with the task link.