docs: update slash command and permission pattern docs for recent changes#3794
Merged
Conversation
trungutt
approved these changes
Jul 23, 2026
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
3 participants
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.
Two doc gaps identified in merged PRs from the last 36 hours, each committed atomically.
Commit 1 — slash commands: HTTP API behavior (refs #3782)
docs/configuration/commands/index.md: the existing "Behavior differs by frontend" callout described full TUI, lean TUI, and CLI but omitted the HTTP API. PR #3782 added server-side resolution of agent-switching slash commands inRunSession— when a user message sent viaPOST /api/sessions/:id/agent/:agentbegins with a slash command whoseagentfield is set, the agent is switched and the message is rewritten before the turn runs. The callout now includes this.Commit 2 — permissions: colon-in-value parsing behavior (refs #3767)
docs/configuration/permissions/index.md: PR #3767 fixed a parser bug where colons inside argument values (e.g. URLs) truncated the value at the first colon. A NOTE is added to the Argument Matching section documenting that only:key=token boundaries split a pattern — colons within a value are preserved — and advising users to check a tool's actual argument names and types before writing argument-matching rules.PRs reviewed: