Tag @dash0 in a Slack channel and Agent0 answers in the thread. It reads the same telemetry you see in Dash0, so you can investigate where the conversation already is.

1
@dash0 why is the checkout service slow?

That's all you need to do. If Agent0 needs anything else from you, it says so in its reply.

Get Started

Invite the bot to a channel and tag it:

12
/invite @dash0
@dash0 how are my services doing?

If Agent0 needs to know which data the channel is about, or who you are in Dash0, it asks and gives you the button or link. See What Agent0 Might Ask For.

The Slack app itself is installed once per workspace by an admin. See Set Up Slack Integration.

What You Can Ask

Service health. @dash0 is the checkout service healthy right now?
Error spikes. @dash0 errors in payment-api went up around 14:00. What changed?
Latency. @dash0 which downstream call is making /checkout slow?
Alerts. Reply in the thread of a Dash0 alert with @dash0 what caused this check to fail? It reads the alert from the thread.
Anything you would ask in the Dash0 UI. Agent0 in Slack is the same agent and can do the same things. Only the UX differs: when it produces a dashboard or a check rule, it links you to the conversation in Dash0 to review and create it, instead of showing the artifact card inline.

Two things make answers better: name the service (the checkout service, not our backend) and give a time range (in the last hour, since the deploy at 14:00).

Whose Permissions Agent0 Uses

Agent0 answers as the person who tagged it. It uses your Dash0 account, so it reads exactly the data you can read and can do exactly what you are allowed to do in Dash0.

This is per message, not per thread. If a colleague tags Agent0 in the same thread, that message runs with their Dash0 permissions, not yours. Two people can get different answers to the same question in the same thread, and that is correct: each answer respects what that person may see.

Answers are visible to everyone in the channel, so a thread is a place where your Dash0 data becomes readable by people who might not have access to it themselves.

What Agent0 may do is the same as if you asked it in the Dash0 UI, including your organization's approval rules for write actions. Slack changes where you ask, not what is allowed.

How It Answers

It adds 👀 to your message while it works, and ✅ when it is done.
A card shows the steps it is taking while it investigates.
The answer lands in a thread under your message, with links back into Dash0.
The footer under the answer names the model level and effort it ran with, for example Standard model, high effort. Its change model link opens Settings → Agent0, where the Slack row sets the default for your next mention. See Model Selection.

Keep Going in the Thread

Reply in the thread and tag it again:

1
@dash0 which endpoint is the slowest?

Each Slack thread is one conversation. Agent0 remembers what it already answered there, so short follow-ups work.

Agent0 starts from the thread it was tagged in. Tag it inside an existing thread and it reads that thread from the start, including what was said before anyone tagged it. Tag it on a new channel message and that message starts the thread, so there is no earlier context to read.

It can also look up other messages when a question needs them, but only in channels the bot was invited to. See What Permissions Are Granted.

Ask one thing at a time. Follow-ups in the thread are faster and more accurate than one long prompt.

What Agent0 Might Ask For

Which Data to Use

The first time anyone tags the bot in a channel, or the first time you message it directly, it does not know which data the conversation is about. It replies with a Configure Dash0 button.

Click Configure Dash0.
Pick the organization and dataset.
Submit. Agent0 answers the original question right away.

In a channel, the choice applies to everyone there, so the whole channel gets answers from the same data. In a direct message it applies only to you. To change it later, use the button Agent0 offers in its replies.

Tip

Point each channel at the dataset its team already works in. A #platform-prod channel and a #platform-staging channel can use different datasets in the same organization. Your direct messages are independent of all of them.

Who You Are

Agent0 answers as you, so it needs to know which Dash0 account you are. The first time you tag it, it sends you a private message with a link. Open it, confirm, and tag Agent0 again.

Once per workspace. See Whose Permissions Agent0 Uses.

To disconnect, post in a channel or send it in a direct message:

1
@dash0 /unlink-me

Good to Know

Direct messages work too. Message the app directly and skip the tag. Everything else is the same.
Automations come first in a channel. If your message matches an enabled Slack automation trigger, that automation runs instead. See Configure Slack Triggers.
Long threads are truncated. Agent0 reads up to 50 replies per mention.
People only. It ignores mentions from other bots and from itself.
One organization and dataset per conversation. Different channels can point at different organizations. Your direct messages have their own, used only by you. Use the Configure Dash0 button to change what a conversation uses.

Ask Agent0 in a Slack Channel