docs: update Slack agent page with recently shipped capabilities

[mintlify]

Documentation changes

Updates /agent/slack to reflect capabilities that have shipped but weren't documented. Closes DOC-437.

• Adds a note under Connect your Slack workspace that Bitbucket Cloud deployments aren't supported and calls out the static egress IP (54.242.90.151) for IP-allowlisted Git servers.
• Notes that you can share a pull request link in any connected deployment to switch context and continue the PR.
• Documents the read-only fast path for question-only requests.
• Reframes Manage automations so the agent and Automations are described as one system, and adds a Trigger automations from Slack messages subsection.
• Documents that follow-up commits on generated PRs get a describing comment plus reviewer rotation.
• Adds a Use the agent outside of channels and DMs section covering the Slack sidepanel, @kb, Linear issue mentions, and @mintlify on GitHub pull requests.

Closes DOC-437

---

For Reviewers

When reviewing documentation PRs, please consider:

✅ Technical accuracy

• Code examples work as written
• Commands and configurations are correct
• Links resolve to the right destinations
• Prerequisites and requirements are accurate

✅ Clarity and completeness

• Instructions are clear and easy to follow
• Steps are in logical order
• Nothing important is missing
• Examples help illustrate the concepts

✅ User experience

• A new user could follow these docs successfully
• Common gotchas or edge cases are addressed
• Error messages or troubleshooting guidance is helpful

---

Generated by Mintlify Agent.

Requested by: patrick@mintlify.com via Slack
Mintlify session: slack_1789770608.833379_C09TP13PJTH

---

Note

Low Risk
Documentation-only updates to the Slack agent page with no runtime or security code changes.

Overview
Updates the Slack agent docs (agent/slack.mdx) to match recently shipped behavior and setup constraints.

Under Connect your Slack workspace, a new note states the Slack agent is not supported on Bitbucket Cloud and documents the Mintlify egress IP (54.242.90.151) for IP-allowlisted Git hosts, with support opt-in.

Multi-deployment and PR continuation are expanded: sharing a PR link can switch deployment and continue work; Continue an automation run now describes full run context, continuing any Mintlify PR from a new thread, and code-change automations commenting on the triggering code PR and rotating reviewer assignment.

Manage automations is reframed so Slack and dashboard automations share the same agent (including troubleshoot/run examples), plus a new Trigger automations from Slack messages subsection (channel triggers, /invite @mintlify).

Roles clarifies viewers are always read-only for Mintlify tools. A new Use the agent in the Slack sidepanel section documents side-panel chat with the same permissions and review flow as channel/DM usage.

^{Reviewed by Cursor Bugbot for commit a418530. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
mintlify	🟢 Ready	View Preview	Sep 19, 2026, 12:14 AM

[ethanpalm]

Pushed corrections after verifying claims against mintlify/server:

• Removed the Linear-issue and GitHub-PR @mintlify mention claims — the Linear agent integration was removed as deprecated (server#7536, zero traffic), and no GitHub PR-mention webhook handler exists in the codebase. Kept only the verified Slack sidepanel capability and dropped the unverified @kb name.
• Fixed the follow-up-PR-comment direction: the comment is posted on the triggering code PR linking to the docs PR, not appended to the docs PR describing changes.
• Softened "rotates the assigned reviewer" to describe actual behavior: it tries the code PR's author/committers in order until one accepts, not a rotation pool.
• Folded in Agent image capabilities #7430's Viewers-role wording fix and closed that PR as superseded.

Still unverified and worth a quick confirm before merge: the exact static egress IP (54.242.90.151) and whether Bitbucket exclusion surfaces a user-facing error vs. silent failure. Left those as-is since they weren't in scope for this pass.