> ## Documentation Index > Fetch the complete documentation index at: https://docs.agentsfleet.net/llms.txt > Use this file to discover all available pages before exploring further. # Answer mentions in Slack > Attach a fleet to a Slack channel so it answers when someone mentions agentsfleet there. ## What this does A fleet attached to a Slack channel answers when someone mentions the `agentsfleet` app in that channel. The fleet reads the thread, runs once, and posts its answer as a reply in the same thread. Slack sometimes delivers one mention twice. The second delivery starts no second run. ## Before you begin Connect Slack to your workspace at **Settings → Integrations**. See [Connect a provider](/fleets/connectors) for the full procedure. Invite the `agentsfleet` Slack app to the channel. The app receives mentions only in channels it belongs to. Find the channel identifier (ID) in Slack. Open the channel's details and copy **Channel ID** from the bottom of the **About** tab. It starts with `C` for a public channel or `G` for a private one. ## Steps 1. Add a `mention` trigger for the channel to the fleet's Definition. `` is the channel ID you copied. The entry goes in the `triggers` list under `config["x-agentsfleet"]`, beside the fleet's other triggers: ```json theme={"theme":"vesper"} { "type": "mention", "source": "slack", "channels": [""] } ``` In a chat, you can ask for the same trigger in words, such as "answer mentions in Slack channel ``". [Author a fleet](/fleets/authoring) covers the chat and the Definition file. `channels` holds exactly one channel ID. One fleet answers in one channel. To answer in a second channel, save a second fleet. 2. Review the setup and check that it carries the one `mention` trigger, then save it. ``, ``, and `` come from the review output. ```bash theme={"theme":"vesper"} agentsfleet chat --no-input --save --name --review-digest ``` ```text theme={"theme":"vesper"} ✓ Fleet : active ``` In the dashboard, check **Your fleet setup** and choose **Save fleet**. 3. Mention the app in the channel and ask your question. ```text theme={"theme":"vesper"} @agentsfleet why did the last deploy fail? ``` The fleet reads the thread you asked from and replies in that thread. 4. Start with the fleet's name when the channel has more than one fleet. ```text theme={"theme":"vesper"} @agentsfleet ci-responder why did the build fail? ``` Case does not matter. A `:` or `,` right after the name is ignored. A mention that names no fleet goes only to a fleet that is running and has no `repository_access: write` in its Definition. The table shows which fleet answers a mention. | The channel has | The mention names a fleet | Who answers | | - | - | - | | No attached fleet | No | The channel's own fleet, described below | | One running fleet without write access | No | That fleet | | Several running fleets without write access | No | Nobody. A notice lists the fleets' names. | | Attached fleets, none running without write access | No | Nobody. A notice asks you to name one. | | Any attached fleet | Yes | The named fleet. A paused fleet sends the paused notice. | A fleet whose Definition declares `repository_access: write` answers only when a mention names it. From one mention it can open at most one draft pull request (PR). It cannot merge the PR, mark it ready for review, or change a workflow. ### The channel's own fleet `agentsfleet` creates one fleet per channel the first time a mention reaches no attached fleet or needs a notice. Its name is `slack-channel--`, in lower case. This fleet answers from a model with no tools and no network access. Its budget is `daily_nanos: "1000000000"`, so it spends at most 1 dollar a day. When you ask for something it cannot reach, it tells you to set up a fleet in `agentsfleet chat` with a `mention` trigger for this channel. Its memory belongs to the channel, and no other fleet reads it. It also posts the channel's notices. ## Verify it works 1. Mention the app in the channel. 2. Check that a reply from the fleet appears in the same thread. 3. Open the fleet in the dashboard. Its trigger card reads **Chat mention** with the channel ID. 4. List the fleet's events. `` comes from `agentsfleet list`. ```bash theme={"theme":"vesper"} agentsfleet events ``` ```text theme={"theme":"vesper"} ``` ## Common problems A notice replaces an answer when `agentsfleet` cannot pick one fleet. Each notice names the next step. | Notice starts with | Why | What to do | | - | - | - | | `Several fleets answer in this channel` | The mention named no fleet, and more than one could answer. | Start the message with one of the listed names. | | `The fleets attached here answer only when named` | Every attached fleet has repository write access or is paused. | Start the message with one of the listed names. | | ` is paused and cannot answer` | The named fleet is paused. | Run the `agentsfleet resume` command the notice prints. | A notice appears 30 to 60 seconds after the mention. The fleet reads the first message of the thread and the latest 19 replies. It cuts each message at 2,000 characters and the whole thread at 16,000. In a private channel, the fleet sees only your mention. The Slack app cannot read private channel history. The fleet also answers from the mention alone when Slack does not return the thread within 1.5 seconds. If Slack loses its reply to a posted answer, `agentsfleet` checks the thread before it posts again. The answer appears once. In a private channel `agentsfleet` cannot check, so the answer can appear twice. A fleet you save under the name `slack-channel--` with settings of its own is never used as the channel's own fleet. While it holds that name, a mention that needs the channel's own fleet starts no run. Rename or delete that fleet. A fleet you save under that name with the channel fleet's exact runtime settings counts as the channel's own fleet. It answers in that fleet's place. A mention from a bot, an edited message, or the app's own reply starts no run. A mention from a Slack workspace that is not connected to an `agentsfleet` workspace starts no run. Connect Slack again from **Settings → Integrations**. ## Remove or undo To detach a fleet from the channel, remove its `mention` trigger and apply the change. 1. Open the fleet in the dashboard and choose **Setup → Edit fleet**. 2. Ask the chat to remove the Slack mention trigger. 3. Check that the trigger is gone from **Update fleet setup**, then choose **Save changes**. In the terminal, start the same chat with `agentsfleet chat --fleet --setup-revision --model `. `` is the `setup_revision` field that `agentsfleet --json fleet show ` prints. Ask for the change, then run `/review` and `/apply`. Deleting the channel's own fleet permanently removes its memory, events, and other fleet records. The next mention that needs it creates a new fleet with empty memory. To remove it, run `agentsfleet kill ` and then `agentsfleet delete `. Between the two commands, the channel fleet is killed, and a mention that needs it gets no answer. A channel fleet you stop instead of killing answers with the paused notice until you resume it. ## Related pages * [Connect a provider](/fleets/connectors) * [Author a fleet](/fleets/authoring) * [Install a fleet](/fleets/install) * [Run and control a fleet](/fleets/running) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.