docs(m106): Slack-resident channel bot — changelog, error codes, trigger sources#116
Merged
Merged
Conversation
…ger sources New Jul 02, 2026 changelog entry for the Slack connector: dashboard OAuth connect, one resident fleet per channel, in-thread answers, channel-scoped memory, and the recent-thread re-read. Error-code reference gains the five UZ-SLK rows (statuses from the server registry) and UZ-CONN-001 is generalized beyond GitHub now that two providers share the connect flow. concepts.mdx trigger sources go three → four with the Slack mention. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
indykish
added a commit
to agentsfleet/agentsfleet
that referenced
this pull request
Jul 2, 2026
Feature milestone → minor bump per the release matrix; make sync-version propagated build.zig.zon + cli/package.json, make check-version green. The user-facing story ships in the docs changelog (agentsfleet/docs#116). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
…ap note, Slack event sub-section - concepts.mdx: drop Slack from the Webhook trigger examples (it has its own dedicated trigger) and say explicitly that a Slack mention does not use the webhook path. - error-codes.mdx: explain the UZ-SLK-021 numbering gap (superseded by the generic UZ-CONN-002 before release); split the four Slack runtime event-handling codes (010/011/020/030) into their own sub-section so operators diagnosing a live channel-bot failure don't scan past them in the OAuth connect & mint table. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019f21a9-2d57-7365-b40e-7ef128491cbb Co-authored-by: Amp <amp@ampcode.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
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.
What
The Jul 02, 2026 changelog entry for the Slack-resident channel bot, plus the reference updates the feature touches:
changelog.mdx— new<Update>: dashboard OAuth connect (no token paste), one resident fleet per channel, in-thread answers, channel-scoped memory, best-effort recent-thread re-read (20 messages), the four/v1/…connectors/slack…routes with scopes, and the new error codes.api-reference/error-codes.mdx— five newUZ-SLK-*rows (statuses taken from the server error registry: 401/401/200/502/502);UZ-CONN-001generalized beyond GitHub now that two providers share the connect flow.concepts.mdx— trigger sources go three → four with the Slack mention.Why
Ships with agentsfleet/agentsfleet#468 (M106). The API reference itself is generated from the product repo's
public/openapi.json; connector routes are deliberately not in it (matching the GitHub-connector precedent — dashboard OAuth + signature-authed ingress, not Bearer surfaces), so the changelog + error codes carry the public story.🤖 Generated with Claude Code
Greptile Summary
Adds the M106 Slack-resident channel bot documentation across four files: a Jul 02, 2026 changelog entry, five new
UZ-SLK-*error codes (split across an OAuth section and a new "Slack event handling" subsection), a fourth trigger source in concepts, and a sidebar rename from "Fleet bundles" to "Fleet templates" in the navigation config. All three issues raised in the previous review round were addressed ineb76810before this revision landed.changelog.mdxintroduces the full feature narrative (dashboard OAuth connect, one fleet per channel, in-thread replies, channel-scoped memory, 20-message re-read), the four new/v1/…connectors/slack…routes with their scopes, and a summary of the new error codes.api-reference/error-codes.mdxaddsUZ-SLK-022to the connect/mint table, a new "Slack event handling" subsection for the four runtime codes, a numbering-gap explanation forUZ-SLK-021, and a generalizedUZ-CONN-001description that now covers both GitHub and Slack.concepts.mdxbumps the trigger-source count to four and adds the Slack mention bullet with a note that it does not share the generic webhook path.Confidence Score: 5/5
Documentation-only change with no runtime logic; safe to merge.
All four changed files are purely documentation — changelog prose, error-code reference rows, a concepts accordion update, and a sidebar navigation config. No code paths, schemas, or executable logic are touched, and all three issues from the previous review round were addressed before this revision arrived.
docs.json retains GET /v1/fleets/bundles under the renamed Fleet templates group — worth confirming whether that endpoint path was preserved or also renamed server-side.
Important Files Changed
Sequence Diagram
%%{init: {'theme': 'neutral'}}%% sequenceDiagram participant U as User (Dashboard) participant API as agentsfleet API participant Slack as Slack OAuth / Events API Note over U,Slack: Connect flow (UZ-SLK-022 / UZ-CONN-001 / UZ-CONN-002) U->>API: "POST /v1/workspaces/{workspace_id}/connectors/slack/connect" API-->>U: "{ authorizeUrl, state (signed, single-use) }" U->>Slack: Browser redirect to authorize page Slack-->>API: "GET /v1/connectors/slack/callback?code=...&state=..." API->>Slack: Token exchange (code to bot token) Slack-->>API: bot token API-->>API: Vault bot token in workspace U->>API: "GET /v1/workspaces/{workspace_id}/connectors/slack" API-->>U: "{ status, team }" Note over U,Slack: Event ingestion (UZ-SLK-010 / -011 / -020 / -030) Slack->>API: POST /v1/connectors/slack/events (HMAC signed) API->>API: Verify signature and timestamp (5-min window) alt Signature invalid - UZ-SLK-010 API-->>Slack: 401 else Timestamp stale - UZ-SLK-011 API-->>Slack: 401 else Team not installed - UZ-SLK-020 API-->>Slack: 200 acknowledged and ignored else Valid event API-->>Slack: 200 acknowledged API->>API: Wake or create channel-resident fleet API->>Slack: Post answer to thread via chat:write alt Delivery fails - UZ-SLK-030 API->>API: Log and retry with backoff end end%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%% sequenceDiagram participant U as User (Dashboard) participant API as agentsfleet API participant Slack as Slack OAuth / Events API Note over U,Slack: Connect flow (UZ-SLK-022 / UZ-CONN-001 / UZ-CONN-002) U->>API: "POST /v1/workspaces/{workspace_id}/connectors/slack/connect" API-->>U: "{ authorizeUrl, state (signed, single-use) }" U->>Slack: Browser redirect to authorize page Slack-->>API: "GET /v1/connectors/slack/callback?code=...&state=..." API->>Slack: Token exchange (code to bot token) Slack-->>API: bot token API-->>API: Vault bot token in workspace U->>API: "GET /v1/workspaces/{workspace_id}/connectors/slack" API-->>U: "{ status, team }" Note over U,Slack: Event ingestion (UZ-SLK-010 / -011 / -020 / -030) Slack->>API: POST /v1/connectors/slack/events (HMAC signed) API->>API: Verify signature and timestamp (5-min window) alt Signature invalid - UZ-SLK-010 API-->>Slack: 401 else Timestamp stale - UZ-SLK-011 API-->>Slack: 401 else Team not installed - UZ-SLK-020 API-->>Slack: 200 acknowledged and ignored else Valid event API-->>Slack: 200 acknowledged API->>API: Wake or create channel-resident fleet API->>Slack: Post answer to thread via chat:write alt Delivery fails - UZ-SLK-030 API->>API: Log and retry with backoff end endReviews (3): Last reviewed commit: "docs: align fleet template API navigatio..." | Re-trigger Greptile