Skip to content

slack.md

Latest commit

 

History

History
97 lines (64 loc) · 3.04 KB

slack.md

File metadata and controls

97 lines (64 loc) · 3.04 KB
Raw

Slack channel setup

Connect a Slack bot to your conductor for channel-based monitoring and control. The bot listens in a dedicated channel and replies in threads to keep the channel clean.

What you need

  • A Slack workspace where you can install apps
  • A conductor already created (agent-deck conductor setup <name>)

Step-by-step setup

1. Create the Slack app

  1. Go to api.slack.com/apps and create a new app.
  2. Enable Socket Mode -> generate an app-level token (xapp-...).
  3. Under OAuth & Permissions, add bot scopes: chat:write, channels:history, channels:read, app_mentions:read.
  4. Under Event Subscriptions, subscribe to bot events: message.channels, app_mention.
  5. (Optional) If using slash commands, create: /ad-status, /ad-sessions, /ad-restart, /ad-help.
  6. Install the app to your workspace.
  7. Invite the bot to your channel (/invite @botname).

2. Run conductor setup (or re-run it)

agent-deck conductor setup <name>

Answer y at the Slack prompt and provide:

  • Bot token (xoxb-...) — from OAuth & Permissions page
  • App token (xapp-...) — from Socket Mode settings
  • Channel ID (C01234...) — right-click channel name -> "Copy link", the ID is in the URL

3. Restart the conductor

agent-deck session restart conductor-<name>

4. Verify

In your Slack channel, type:

/ad-status

The bot should reply with an aggregated status across all conductors.

Available commands

The Slack bot supports both prefix routing and slash commands:

Command What it does
<name>: <message> Routes message to a specific conductor
/ad-status Aggregated status across all profiles
/ad-sessions List all sessions
/ad-restart [name] Restart a conductor
/ad-help List available commands

Responses come in threads to keep the channel clean.

One bot per conductor

The same constraint applies as with Telegram: each conductor needs its own dedicated Slack bot. Do not share a single bot across multiple conductors.

Configuration

Slack credentials are stored alongside other conductor settings. The bridge daemon handles Slack and Telegram concurrently — both can run simultaneously.

Debugging tips

Bot does not respond

  1. Verify Socket Mode is enabled (not HTTP webhooks).
  2. Confirm the bot is invited to the channel.
  3. Check that event subscriptions include message.channels and app_mention.
  4. Check bridge logs: tail -f ~/.local/share/agent-deck/conductor/bridge.log

Slash commands return "dispatch_failed"

This means Slack cannot reach your app. With Socket Mode enabled, Slack should deliver slash commands over the WebSocket — verify the app-level token is correct and the bridge is connected.

Messages appear but conductor does not reply

Verify the conductor session is running:

agent-deck conductor status <name>

Check that routing is correct — the Slack bot uses the same name: message prefix convention as Telegram.