Skip to content

Agent and automations UI updates - #6822

Merged
ethanpalm merged 5 commits into
mainfrom
docs/slack-agent-manage-automations
Jul 30, 2026
Merged

Agent and automations UI updates#6822
ethanpalm merged 5 commits into
mainfrom
docs/slack-agent-manage-automations

Conversation

@ethanpalm

@ethanpalm ethanpalm commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

Documentation changes

Revises the agent and automation pages for recent UI changes

Closes DOC-401: Update agent/automations docs for dashboard changes


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

Note

Low Risk
Documentation-only changes with no code or runtime behavior impact.

Overview
Updates agent and automations documentation to match recent Automations dashboard and Slack configuration flows.

Review process and Configure Slack paths are clarified: self-hosted Git users open Configure Slack on Automations, then set Review process in Slack settings. The branch-protection note now states the agent still opens a PR when direct pushes are blocked, even if Push to main is selected. Repository access instructions drop the agent panel Settings reference and add Git Settings for GitLab.

Slack docs gain a Manage automations section (create, configure, run, and troubleshoot automations via @mintlify). Create automation adds a tip pointing to that Slack flow.

Automations manage replaces Turn on Slack notifications with Configure Slack, removes several UI screenshots, points run history to ?tab=runs, and renames run statuses to match the product (Review needed, Running, Accepted, Closed, No action needed, etc.).

Reviewed by Cursor Bugbot for commit 588ab5e. Bugbot is set up for automated code reviews on this repo. Configure here.

The Slack agent can now create, configure, enable/disable, and run
automations, and answer questions about run history and credit usage,
per the automations-unification announcement (2026-07-24).
The Configure Slack modal is titled "Slack settings" and the removed
Agent page had no equivalent "agent panel Settings" for repo access.
Also correct the branch-protection note: the dashboard no longer hides
the Review process setting, but the agent still opens a PR when the
deploy branch requires one, regardless of the setting.
@ethanpalm

Copy link
Copy Markdown
Collaborator Author

noting broken links are expected from removing images. will be fixed when translations run and removes the paths for the localized pages

@ethanpalm
ethanpalm merged commit 5818fbe into main Jul 30, 2026
1 of 2 checks passed
@ethanpalm
ethanpalm deleted the docs/slack-agent-manage-automations branch July 30, 2026 22:57
@mintlify

mintlify Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
mintlify 🔴 Failed Jul 30, 2026, 10:58 PM

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
tomee 🔴 Failed Jul 30, 2026, 10:58 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

ethanpalm added a commit that referenced this pull request Jul 30, 2026
…#6826)

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants