Alpheous·
Operator Console

Slack Channels

Slack Channels controls which channel each agent posts to, and lets you confirm that a channel is actually reachable. Bot tokens themselves are set on the Connections page; this screen only shows whether they're present, and manages where each agent's messages go once they are.

A summary at the top shows how many agents have a resolved channel, how many bot tokens are configured, and how many agents actually post to Slack at all. Not every agent ships a card: some only ever work in the background.

The Bindings Table

Each row lists an Agent, the account it posts as, and its Channel, with a Test action next to it. A status badge on each row tells you what to expect: Posts means the agent sends cards to that channel; No card means the agent doesn't post anything on its own; Override means this install has set a channel different from that agent's default; and "Posts but unwired" flags an agent that is meant to post but has no channel resolved yet, worth fixing before you rely on it.

An explicit override you set here always wins over an agent's default channel.

Testing a Channel

Use Test to confirm a channel is actually reachable: it probes the channel live and reports back the resolved channel name, noting if it's private, or tells you the channel is unreachable so you can fix it before your team misses something important.

  • Connections: where the Slack workspace and bot token behind these bindings are set up.
  • Notifications: notifications that route to Slack rely on the same channel bindings managed here.