docs: sync /docs with changes merged 2026-05-28 – 2026-05-29#2929
Merged
Conversation
gtardif
previously approved these changes
May 29, 2026
dgageot
approved these changes
May 29, 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
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.
Summary
Catch-up documentation updates for code changes merged in the last 36 hours.
Commits
docs: document /api/mcp-oauth/callback endpoint and --mcp-oauth-redirect-uri flag(refs #2896, #2921)File:
docs/features/api-server/index.mdAdded a new
### OAuthsubsection documentingPOST /api/mcp-oauth/callback(query parameters, error responses 400/404) and added--mcp-oauth-redirect-urito the API-server CLI flags table.docs: clarify docker-agent/authorize_url prose in unmanaged OAuth section(refs #2921)File:
docs/features/remote-mcp/index.mdFixed ambiguous prose: "opens the browser at
docker-agent/authorize_url" → "at the URL provided in thedocker-agent/authorize_urlmeta field".docs: document full elicitation meta for client-driven unmanaged OAuth flow(refs #2896)File:
docs/features/remote-mcp/index.mdThe client-driven (flag-not-set) case previously said it "emits only
auth_server_metadata+resource_metadata", which was inaccurate. The code emits five keys for both sub-behaviors. Replaced the prose description with a proper table showing all five keys (docker-agent/type,docker-agent/server_url,auth_server,auth_server_metadata,resource_metadata).docs: add --app-name example to TUI launch section(refs #2914)File:
docs/features/tui/index.md--app-namewas added to the CLI flags table by #2927 but was absent from the TUI launch examples block. Added the example.docs: fix /api/mcp-oauth/callback 400 condition and add error-path params(refs #2896)File:
docs/features/api-server/index.mdThe original endpoint description said "Returns 400 if
stateorcodeis missing" — incorrect per the handler (mcpOAuthCallbackinpkg/server/server.go). The handler accepts?error=<error>as a valid alternative to?code, per the OAuth error-response path (RFC 6749 §4.1.2.1), and returns 400 only if bothcodeanderrorare absent. Fixed the 400 condition and documented the full query-string contract including?errorand?error_description. Also aligned the--mcp-oauth-redirect-uriflag description with the fuller version indocs/features/cli/index.md(adds "and sends the full authorize URL to the client via elicitation").PRs covered
POST /api/mcp-oauth/callbackendpoint docs (accurate 400 condition, full query params); full elicitation meta table for client-driven path;--mcp-oauth-redirect-uriflag description aligned--app-nameflag--app-nameexample added to TUI launch docscagent/todocker-agent/cagent/*meta key refs removed (verified complete)--sidebarflag--disable-commandsflagafter_llm_callhook payloadmodel_iddocumented