docs(fleets): mention a fleet in Slack and it answers in the thread (M206) - #205
Merged
Merged
Conversation
… the thread A new how-to page covers attaching a fleet with `--slack-channel`, how a mention picks a fleet, the channel's own fleet, notices, thread limits, and detaching. Install, authoring, connectors and the command-line reference link to it. The error registry marks `UZ-SLK-010`, `UZ-SLK-011` and `UZ-SLK-020` retired: the Rust daemon answers `UZ-WH-010`/`UZ-WH-011` for Slack as for every signed route, and ignores an unmapped team with `team_not_mapped`. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…nd the trigger card names the channel Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…in its place Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ll-only fleet under the channel fleet's name answers as it Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Review on #205: - The routing table said one attached fleet answers an unnamed mention. Only a running fleet without repository write access does; attached fleets none of which qualify earn a notice asking for a name, and a named paused fleet sends the paused notice. - The trigger example is a fragment for an existing TRIGGER.md, and says so. - Between kill and delete, the channel fleet is killed and answers nothing; a stopped one sends the paused notice until resumed. - Posting a Slack answer needs no grant; calling another provider, such as GitHub for a draft pull request, still does. - The accepted-mention response example is valid JSON. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…s list Review on #205: the lead-in said to add the lines to the x-agentsfleet block while the snippet opens with x-agentsfleet, so pasting it nested a second block. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Paired with agentsfleet #714.
Changes
fleets/slack.mdx(new, indocs.json): mention a fleet in a Slack channel and it answers in the thread. Covers attaching a fleet, the channel's own fleet, notices, what the fleet reads from the thread, private channels, and the lost-reply check before a retry.changelog.mdx: a Sep 24<Update>for the Slack mention flow.fleets/install.mdx,cli/agentsfleet.mdx:agentsfleet install --slack-channel <CHANNEL_ID>.fleets/connectors.mdx,fleets/authoring.mdx: Slack as a mention trigger.api-reference/error-codes.mdx:UZ-SLK-010,UZ-SLK-011andUZ-SLK-020are marked retired. A bad signature and a stale timestamp now answer the sharedUZ-WH-010andUZ-WH-011; an unmapped team answers200with{"ignored": "team_not_mapped"}.Verified
make lintpassed (exit 0):Ran 22 tests ... OK,Documentation check passed,openapi drift check clean,success no broken links found.🤖 Generated with Claude Code
The PR appears safe to merge; no outstanding finding or new actionable issue was identified.
Summary
The PR documents how fleets answer Slack mentions, adds setup and navigation guidance, and updates the changelog and error-code reference. The change since the previous review clarifies that readers should add only the
mentionentry to an existing trigger list; no new actionable issue was found.Reviews (3) · Last reviewed commit: "docs(fleets): the trigger example is mer..."