Slack

Lobu’s Slack adapter supports assistant threads, rich UI, and interactive workflows.

GeneralLegalEngineeringSupportFinanceSalesLeadershipAgent CommunityMarket IntelligenceVenture Capital

C

Coding

online

List open PRs in lobu-ai/lobu12:01

Can't reach github.com — not in the agent's allowed domains. Grant access?12:01

Allow github.com

Allow for 1 hour12:01

Added github.com to allowed domains. 3 open PRs in lobu-ai/lobu: • #214 Fix worker memory leak • #219 Telegram adapter retries • #223 Add Bedrock provider12:01

O

Ops Assistant

online

Summarize my active Linear sprint12:01

I need the `linear` skill to query Linear. It bundles the Linear MCP and handles OAuth via Lobu.12:01

Install linear

Go ahead12:01

Installed and connected. Sprint "Week 15" (68% done): • 11 merged, 3 in review, 2 todo • Blocked: AUTH-234 (design) • At risk: API-89 (due tomorrow)12:01

A

Assistant

online

Switch to Claude Sonnet12:01

You can change the model from your settings — opens a scoped page with your current agent config.12:01

Open Settings

Done — set to claude-sonnet-4-612:01

Now running on claude-sonnet-4-6 via OpenRouter. Next messages will use the new model.12:01

Setup

Single-workspace setup

1. Create a Slack app at api.slack.com/apps and install it to your workspace.
2. Copy the Signing Secret and Bot Token (xoxb-...) from the app settings.
3. Run lobu connections add slack to add the connection to your existing agent (prompts for the bot token and signing secret), or run lobu init to scaffold a new project and pick Slack in the wizard.
4. Start the stack with lobu run -d — the bot is now live in your Slack workspace.

Installation Modes

Lobu supports two Slack installation models:

• Single-workspace connection for self-hosted deployments. You create your own Slack app, install it to one workspace, then configure Lobu with the Signing Secret and Bot Token.
• OAuth / multi-workspace distribution for shared deployments. In this mode, users install a shared Slack app through an install link, Slack redirects back to Lobu, and Lobu creates or updates one Slack connection per Slack workspace.

For OAuth distribution, incoming Slack events are routed by Slack team_id, so each installed workspace is isolated behind its own Lobu connection even when many workspaces share the same app.

Shared OAuth distribution

If you want one Slack app that many workspaces can install, create the app for your public Lobu deployment and wire Slack back to these Lobu endpoints:

• Install URL for users: https://<your-lobu-base-url>/slack/install
• OAuth redirect URL: https://<your-lobu-base-url>/slack/oauth_callback
• Events / interactivity / slash commands URL: https://<your-lobu-base-url>/slack/events

Minimum setup:

1. Create a Slack app for your public Lobu domain.
2. Configure the app’s OAuth redirect URL to https://<your-lobu-base-url>/slack/oauth_callback.
3. Point event subscriptions, interactive requests, and slash commands to https://<your-lobu-base-url>/slack/events.
4. Add the bot scopes your Lobu deployment needs.
5. Configure Lobu with the Slack app’s Client ID, Client Secret, and Signing Secret.
6. Share https://<your-lobu-base-url>/slack/install with users who should install the app to their Slack workspace.

When a user completes the Slack install flow, Lobu exchanges the OAuth code, stores the workspace installation, and creates or updates the Lobu Slack connection for that workspace automatically.

Configuration

Field	Required	Type	Description
botToken	No	string	Bot token (xoxb-...). Required for single-workspace mode.
botUserId	No	string	Bot user ID (fetched automatically if omitted).
signingSecret	No	string	Signing secret for webhook verification.
clientId	No	string	Slack app client ID (required for OAuth / multi-workspace).
clientSecret	No	string	Slack app client secret (required for OAuth / multi-workspace).
encryptionKey	No	string	Base64-encoded 32-byte AES-256-GCM key for encrypting stored bot tokens.
installationKeyPrefix	No	string	State key prefix for workspace installations (default: slack:installation).
userName	No	string	Override bot username.

Connection Settings

These settings apply to all platform connections and are passed in the settings object.

Field	Required	Type	Description
allowFrom	No	string[]	User IDs allowed to interact with this connection. Omit to allow all; empty array blocks all.
allowGroups	No	boolean	Whether group messages are allowed (default true).
userConfigScopes	No	string[]	Scopes that end users are allowed to customize. Empty = no restrictions.

Features

• Block Kit rendering — cards, sections, action buttons, and link buttons are emitted as real Slack Block Kit by the @chat-adapter/slack adapter. Agents never author Block Kit JSON directly; they post platform-agnostic chat elements and the adapter converts.
• Thread streaming using Slack streaming APIs for incremental responses.
• Tool approval UI — the gateway intercepts destructive MCP tool calls and renders an in-thread approval card (Allow once / 1h / 24h / Always / Deny) before executing. See below.
• AskUser — agents can prompt the user with an action-button card (AskUserQuestion(question, options[])); each option renders as a Block Kit button in-thread.
• MCP tool access — workers discover MCP tools at startup and call them through the gateway proxy; responses render inline as system messages.
• Settings/auth links rendered as platform-scoped link buttons.
• Thread status indicator (is running..) with rotating progress messages.

Destructive Tool Approval

By default, destructive MCP tool calls require in-thread user approval. Lobu uses the MCP protocol’s tool annotations:

• A tool with readOnlyHint: true or destructiveHint: false runs without approval.
• Any other tool (including tools with no annotations) triggers an approval card in the thread. The user picks Allow once / 1h / 24h / Always / Deny, and the choice is recorded in the grant store for future calls.

This is the conservative default from the MCP spec — tools are presumed destructive unless they say otherwise.

Operator override ([agents.<id>.tools])

If you want specific MCP tools to skip the approval prompt, configure pre_approved under [agents.<id>.tools] in lobu.toml.

See Tool Policy for the behavior and lobu.toml reference for the schema.

Typical Use Cases

• Team assistant inside channels and DMs.
• Human approval steps for domain grants or agent decisions.
• Rich in-thread interaction without leaving Slack.