> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/use-groundcover/connectors/slack/slack-agent.md).

# @groundcover Agent in Slack

{% hint style="info" %}
This capability is only available to BYOC deployments. Check out our [pricing page](https://www.groundcover.com/pricing) for more information about subscription plans and the available deployment modes.
{% endhint %}

Once the [Slack connector](/use-groundcover/connectors/slack.md) is set up and you have [connected your personal Slack account](#connecting-your-personal-slack-account), you can interact with groundcover's Agent from any Slack channel where the groundcover app is present by mentioning **@groundcover**.

This gives your team a shared interface for investigating issues, querying observability data, and triaging alerts — without leaving Slack.

## How It Works

1. In any Slack channel where the groundcover app is present, type `@groundcover` followed by your question or request.
2. The Agent processes your message and replies in a thread under your message.
3. You can continue the conversation in the thread — the Agent maintains context within that thread, just like a regular [Agent Mode](/use-groundcover/agent-mode.md) session.

The Agent in Slack has the same capabilities as Agent Mode in the groundcover UI: investigating issues, querying logs/traces/metrics, creating monitors and dashboards, and more. See [Agent Mode](/use-groundcover/agent-mode.md) for the full list of capabilities.

{% hint style="info" %}
The Agent responds in a thread to keep the channel clean. All follow-up messages in that thread are part of the same conversation context.
{% endhint %}

## Identity, Permissions & Budget

Every `@groundcover` mention is tied to the **Slack user who sent the message**. The Agent runs as that user's agent session, which means:

| Aspect       | Behavior                                                                                                                                                                                                                                                                         |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Identity** | The Agent session is associated with the groundcover user whose personal Slack account matches the Slack user who sent the message                                                                                                                                               |
| **RBAC**     | The Agent can only access data the mentioning user is authorized to see, based on their [RBAC configuration](/use-groundcover/role-based-access-control-rbac.md). If the user's role restricts them to specific namespaces or clusters, the Agent respects those same boundaries |
| **Budget**   | The request counts against the mentioning user's [Agent Mode budget](/use-groundcover/agent-mode/cost-management.md). If the user has reached their monthly limit, the Agent will not process the request                                                                        |

{% hint style="warning" %}
**Visibility:** While the Agent enforces the mentioning user's permissions for data access, the Agent's response is visible to **everyone in the Slack channel**. Be mindful when querying sensitive data in public or broadly-shared channels — the response will be visible to all channel members, even those who may not have the same level of access in groundcover.
{% endhint %}

### What Happens If You're Not Connected

If a Slack user mentions `@groundcover` but has not [connected their personal Slack account](#connecting-your-personal-slack-account), the Agent will respond with a message asking them to connect their account first. The Agent cannot process requests from unconnected users because it has no way to determine which groundcover user they are.

## Connecting Your Personal Slack Account

Before you can use `@groundcover` mentions, you need to link your personal Slack account to your groundcover user. This is a one-time setup.

1. In groundcover, go to **Integrations → Connectors → My Connections**.
2. Find **Slack** and locate the Slack App for the workspace you want to connect to.
3. Click **Connect**.
4. You are redirected to Slack to sign in and approve access.
5. Once approved, you are redirected back to groundcover. Your Slack identity is now linked to your groundcover account.

{% hint style="info" %}
You must sign into the same Slack workspace that the admin authorized during the [Slack connector setup](/use-groundcover/connectors/slack.md#step-4-authorize-the-app-oauth). Signing into a different workspace will fail.
{% endhint %}

To disconnect, click **Disconnect** on the Slack App entry in **My Connections**. You can reconnect at any time.

### Multiple Workspaces

If your organization has [multiple Slack workspaces connected](/use-groundcover/connectors/slack.md#connecting-multiple-slack-workspaces), you can connect your personal account to each one independently. The Agent will respond to your mentions in any workspace where your account is linked.

## Tips

* **Be specific** — the Agent works best with clear, specific questions. Instead of "what's wrong?", try "why is the checkout service throwing 500 errors in the production cluster?"
* **Use threads for follow-ups** — continue the conversation in the same thread to maintain context. Starting a new top-level mention creates a new, independent session.
* **Channel selection** — use a dedicated channel (e.g., `#groundcover-agent`) for agent interactions to keep other channels focused. The Agent works in any channel it has been added to.
* **Private channels** — the Agent can respond in private channels, but it must first be invited to the channel. Run `/invite @groundcover` to add it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.groundcover.com/use-groundcover/connectors/slack/slack-agent.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.