---
title: "Run a persistent AI agent in Slack — AgentSky"
description: "Connect a selected AgentSky agent to Slack. Review setup and permissions, verify a team task, and learn when a native bot is a better fit."
url: https://agentsky.dev/use-cases/slack-agent
---

[Log in](https://agentsky.dev/auth/start?returnTo=%2Fuse-cases%2Fslack-agent) [Sign up](https://agentsky.dev/auth/start?returnTo=%2Fuse-cases%2Fslack-agent&mode=signup)

[All use cases](https://agentsky.dev/use-cases)

# Your team's agent, in Slack

Teammates reach one shared agent from Slack, Telegram or Discord.

[Set up Slack](https://agentsky.dev/channels/slack) [See tutorials](https://agentsky.dev/tutorials)

## Starter prompt

```
Watch [#channel]. When someone posts [the trigger], do [the job] and reply in the thread with what you did.
Ask in the thread before anything that cannot be undone.
```

Your team doesn't run Claude Code. They use Slack.

ConnectHermes + DeepSeek V4 Pro

## Related

- [Hermes in the catalog](https://agentsky.dev/agents/hermes)
- [See capability details](https://agentsky.dev/docs/channels)
- [Run it from the API](https://agentsky.dev/developers)
- [What a run costs](https://agentsky.dev/pricing)

## Choose something else when

Build a native bot when the job is stateless, needs an unsupported channel, or requires bespoke identity, moderation, and message-routing controls.

## Best for

- Teams that want one persistent hosted agent reachable from supported conversation channels without asking every teammate to adopt a developer tool.
- You bring the which channels to connect.
- You bring the agent and model.
- You bring the instructions and tools.

## How it works

1. Step 1 Choose the agent that answers Connect the intended workspace or bot, and select the answering agent in the dashboard. Each channel has its own authorization or pairing flow.
2. Step 2 Keep task access explicit Give the selected agent the context, tools and application permissions its task needs. Channel authorization does not grant access to unrelated systems.
3. Step 3 Team reaches the agent without onboarding Teammates hand work to the agent in-channel and see results without leaving Slack for each message or learning a separate agent interface.

## What AgentSky runs

- Channel connections across platforms
- Selected agent routing
- Managed agent workspace

## Background agents

The channel settings connect a messaging surface to a selected agent. Verify the connection with a task and a useful reply in the intended workspace.

An AgentSky product workflow linked to the background-agent capability; not independent evidence of adoption, response quality, or channel uptime.

[See capability details](https://agentsky.dev/docs/channels)

---

Markdown copy of https://agentsky.dev/use-cases/slack-agent. Every agentsky.dev page has one: add `.md` to its address or send `Accept: text/markdown`. Start from https://agentsky.dev/llms.txt.