Mention it in any channel
Drop @Levain into a channel it's been invited to and ask. It acknowledges the mention on the spot and gets to work — no command syntax to learn.
Your agents, in Slack.
Mention Levain in a channel and the answer streams into the thread as it's written. Agents ask when they hit a decision only you can make, and post their work where your team already reads.
Ask in the channel. Answered in the thread.
Connect Slack and Levain joins the workspace like a teammate: mention it, question it, and keep the whole exchange where it started.
The thread keeps the context
Follow-ups are replies in the same thread, and each one becomes another turn in the same conversation. Anyone in the thread can jump in — the agent keeps track of what's been asked.
Or open the assistant pane
Levain also sits in Slack's Agents & AI pane. Open it for a direct line: suggested prompts to start from, and a status line that tells you what the agent is doing while you wait.
Replies stream in live.
Levain writes into Slack with native streaming — the answer builds in front of you in real markdown, and long replies arrive whole instead of trimmed to a preview.
Your agents speak up first.
Pick a channel and choose what lands there: a run finished, a run failed, or an agent that needs a human call. Reply in the thread and the paused run resumes exactly where it stopped.
-
Opt in, type by type
Every notification type is off until you turn it on, so the channel carries decisions instead of noise.
-
Reply to resume
Your reply goes straight back into the waiting run — same session, no dashboard detour. A check mark lands on your message once the agent has picked it up.
-
Anyone can answer
The question posts to the channel, and whoever holds the answer replies. The agent takes the first response and moves.
Levain
App
9:41 AM
Invoice Reconciler needs your call: two charges on the Acme account don't match the ledger. Hold the batch, or post the 14 that reconcile?
Maya
9:44 AM
Hold it. I'll check with finance first.
1The check mark is the platform's receipt: the run resumed where it paused, with Maya's answer folded in.
Let the agents do the posting.
Grant an agent the Slack tools and it publishes its own work: the Monday revenue recap into #finance, the changelog into #releases — on a schedule or on demand.
send_message
Post to a channel or reply in a thread. Pair it with a schedule and the agent files its own weekly recap, without a reminder from anyone.
list_channels
Lists the workspace's channels and which ones the bot has joined, so the agent posts to the right room instead of guessing.
One line in a recipe turns the tools on:
# @mcp_servers ["slack"]
Scoped per agent
You grant the tools agent by agent, with an allowlist. A tool you haven't listed is stripped out before the model ever sees it.
Invited channels only
The bot can only post where someone has typed
/invite @Levain. Your team decides the rooms; the
agents work inside them.
Fails politely
If Slack isn't connected yet, the tools hand the agent a plain explanation instead of an error — the run carries on.
Connected in two minutes.
One authorization in the browser. Credentials stay encrypted on the platform — nothing to paste, store, or rotate.
Open Integrations
In the dashboard's Integrations page, click the Slack tile.
Approve in Slack
Your browser walks Slack's standard authorization. Approve it and the workspace is linked — every agent can now be granted Slack access.
Invite and mention
Type /invite @Levain in a channel and mention it.
For proactive posts, pick a default channel under
Settings → Notifications.
Put an agent in the channel.
Sign up, connect Slack from the Integrations page, and ask your first question where your team already works.