Auto-Reply Channels
Agents in Slack used to act only when someone @mentioned them. That's fine for questions. It doesn't help in an alerts channel at 3 am, when the post comes from a monitoring bot and nobody is awake to tag anyone.
How it works
- Open Settings βΊ Slack, pick a channel and switch on Auto-reply. The agent now handles every new top-level post in that channel, whether a person or a bot wrote it. Replies inside a thread still need a tag.
- Each channel has its own agent and mode (Ask or Execute, the same words you type after
/nairi). - A post the agent picks up gets π, then the usual β³ while it works.
- Switching auto-reply on or off posts a short note in the channel, so people there know what changed.
Guardrails
- Hourly limit. A channel runs at most 10 tasks per rolling hour by default, and you can set anything from 1 to 500. Tagged mentions count toward it. Once a channel hits the limit, Nairi posts one note and skips untagged posts for the rest of the hour. Skipped posts are not queued for later.
- Pause all. One switch puts every auto-reply channel back to tag-only. While it's on, the page shows the paused state in yellow.
- No loops. The agent ignores its own posts, so it can't trigger itself.
- Routing stays yours. Inline tags like
[agent=...]or[mode=...]inside an auto-picked post are ignored, so a bot's message can't change which agent runs or how.
Auto-reply isn't available for Slack Connect channels or for channels still waiting for approval.
Keeping an eye on it
The Slack settings page groups channels into Auto-reply, Reply when tagged and Waiting for approval. Selecting an auto-reply channel shows how many runs it has used this hour and its five most recent runs, each linking to the task. Admins can change the settings, and members can see them.
Auto-reply, agent and mode can also be set per channel through the public API's channels endpoints.