Deprecate per-task actions in docs - #15
Merged
Merged
Conversation
Point users to web-UI global actions; add Actions page. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
snopoke
marked this pull request as ready for review
July 9, 2026 12:45
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.
Backend is retiring per-task/API-attached action config in favour of web-UI global actions routed through reusable channels (deprecate-then-remove). This updates the docs to match: per-task action examples (SDK
actions=, CLI--action, APIactionsfield) are removed and replaced with deprecation notices, and a newactions.mdpage documents global actions + channels as configured in the web UI.Deliberately out of scope: no changelog entry (no release version defined yet; the write endpoints/
--actionstill work), and Slack /queue_wait_exceededare not documented since those workstreams aren't confirmed shipped.Verified with
mkdocs build— no broken-link warnings introduced (remaining strict-mode warnings are pre-existing: griffe from the sibling SDK,web_example.mdintentionally outside nav).