docs(docker-agent): sync docs with docker-agent v1.110.0#25478
docs(docker-agent): sync docs with docker-agent v1.110.0#25478aheritier wants to merge 3 commits into
Conversation
❌ Deploy Preview for docsdocker failed. Why did it fail? →
|
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The changes correctly add documentation for twelve new model provider aliases and three new configuration fields (compaction_model, bypass_models_gateway, and tags). No vendored files were touched, no redirects are needed, and no style guide violations (hedge words, AI-isms, marketing language) were found in the new content. The compaction_model NOTE callout is logically consistent and accurate.
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The added documentation for compaction_model, bypass_models_gateway, version, and tags is well-structured, accurate, and proportionate in scope. Three minor style issues were found — all low severity and non-blocking.
|
|
||
| > [!NOTE] | ||
| > If the compaction model has a smaller context window than the primary model, | ||
| > Docker Agent triggers compaction against the smaller window, so the summary |
There was a problem hiding this comment.
[LOW] NOTE callout may confuse readers about compaction behavior
The NOTE describes two scenarios without clearly distinguishing them:
- "If the compaction model has a smaller context window … Docker Agent triggers compaction against the smaller window, so the summary call can always ingest the full conversation." (Describing behavior when a smaller-window model is used — compaction fires early based on the smaller window, so it works.)
- "Pair the primary with a compaction model whose context window is at least as large to keep the proactive trigger aligned with the primary's window." (Recommending against using a smaller-window model.)
The two sentences describe conflicting scenarios without framing one as "here is what happens" and the other as "and here is why you should avoid it." Consider restructuring:
If the compaction model has a smaller context window than the primary model, Docker Agent uses that smaller window to trigger compaction proactively — the summary call can still ingest the full conversation, but compaction fires earlier than expected. Use a compaction model whose context window is at least as large as the primary's to keep the trigger aligned with the primary's window.
| own model to summarize the conversation. That summary call ingests the entire | ||
| conversation and is the slowest, most expensive call in a session. | ||
|
|
||
| You can point `compaction_model` at a smaller, faster model to make compaction |
There was a problem hiding this comment.
[LOW] Informal phrasing "point compaction_model at" — prefer "set compaction_model to"
"You can point compaction_model at a smaller, faster model" uses the informal idiom "point X at Y". The Docker style guide prefers direct, precise language. Consider:
Set
compaction_modelto a smaller, faster model to reduce compaction cost without changing the model that runs the conversation:
| instruction: You are a helpful assistant. | ||
| ``` | ||
|
|
||
| A bypassed model authenticates with its own provider credentials |
There was a problem hiding this comment.
[LOW] Parentheses in prose — consider restructuring
The Docker style guide recommends avoiding parentheses in technical documentation as they reduce readability. The current sentence:
A bypassed model authenticates with its own provider credentials (
OPENAI_API_KEY,ANTHROPIC_API_KEY, or the explicittoken_key) rather than the gateway's token.
Could be rewritten without parentheses:
A bypassed model authenticates directly with its provider using
OPENAI_API_KEY,ANTHROPIC_API_KEY, or the explicittoken_key— not the gateway's token.
|
Since #25480, The content of this PR is already covered upstream:
The pages will appear on docs.docker.com with the next version-pin bump ( |
…76,3384,3385,3337,3389 - add new model providers Add documentation for twelve new built-in provider aliases: Baseten, Cerebras, Cloudflare AI Gateway, Cloudflare Workers AI, DeepSeek, Fireworks AI, Groq, Moonshot AI, OpenRouter, OVHcloud, Together AI, Vercel. Also add compaction_model and bypass_models_gateway model config fields, and tags metadata field.
Document the new TUI agent delegation feedback UI: - Transfer box: animated sidebar box during transfer_task delegation - Return box: reverse-direction animation when control returns to parent - Chat transition: non-persisted return transition line in message stream
0e76bf0 to
0c8afc5
Compare
aheritier
changed the title
Covers changes from the last 36 hours: - feat: add scheduler toolset docs and config entry (docker/docker-agent#3632) - docs: update MCP header templates, add MCP prompts slash commands (docker/docker-agent#3635) - feat: document safe-auto and safer safety policies for safer_shell (docker/docker-agent#3647) - feat: add custom token pricing (cost config) documentation (docker/docker-agent#3664) - feat: document custom base_url implies bypass_models_gateway (docker/docker-agent#3667) - chore: bump docker-agent vendor to v1.110.0 with accumulated changes (thinking budget gpt-5.6, agents config, CLI toolsets command, OpenAI/ChatGPT/Vercel provider updates, background-agents permissions)
aheritier
changed the title
## Summary Automated sync of Docker Agent documentation from the docker/docker-agent repository. **docker-agent version:** v1.110.0 Closes #25478 --- > [!IMPORTANT] > **Reviewer:** Please close and reopen this PR to trigger CI checks. > See: https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/trigger-a-workflow#triggering-a-workflow-from-a-workflow Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
3 participants
Syncs the docker-agent documentation vendor to v1.110.0, covering user-facing changes from the last 36 hours.
Changes
PR #3632 — new scheduler toolset
_vendor/.../docs/tools/scheduler/index.md(new page documenting create_schedule, list_schedules, cancel_schedule, and schedule specs)_vendor/.../docs/configuration/tools/index.mdwith the scheduler table entryPR #3635 — MCP header templates and prompts docs sync
_vendor/.../docs/features/remote-mcp/index.md: per-request header template expansion note (${env.VAR}, ${headers.NAME}), updated DCR fallback section_vendor/.../docs/tools/mcp/index.md: expanded remote.headers description, added MCP Prompts slash-command sectionPR #3647 — safe-auto safety policy
_vendor/.../docs/configuration/hooks/index.md: updated safer_shell entry documenting safe-auto and safer safety policiesPR #3664 — custom token pricing
_vendor/.../docs/configuration/models/index.md: added cost config block, cost property reference row, Custom Token Pricing sectionPR #3667 — custom base_url implies bypass_models_gateway
_vendor/.../docs/configuration/models/index.md: updated bypass_models_gateway property and Gateway Bypass section_vendor/.../docs/providers/custom/index.md: added Global Providers section and gateway bypass noteCatch-up: vendor bump to v1.110.0
PRs reviewed (no doc changes needed)
#3672, #3671, #3670, #3666, #3665, #3663, #3662, #3661, #3659, #3658, #3657, #3656, #3655, #3654, #3653, #3652, #3651, #3650, #3649, #3648, #3645, #3644, #3643, #3642, #3634