Skip to content

docs(docker-agent): update TUI docs and add model providers/config fields#25478

Open
aheritier wants to merge 2 commits into
docker:mainfrom
aheritier:docs/auto-update
Open

docs(docker-agent): update TUI docs and add model providers/config fields#25478
aheritier wants to merge 2 commits into
docker:mainfrom
aheritier:docs/auto-update

Conversation

@aheritier

@aheritier aheritier commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Syncs Docker Agent documentation with changes merged into docker/docker-agent main.

TUI — Agent Delegation Feedback (docker/docker-agent#3611)

Documents the new visual feedback shown during transfer_task delegations:

  • Transfer box: animated sidebar box with traveling dot (≥1.5 s, ≤3 s max)
  • Return box: reverse-direction animation when control returns to parent (≤1.5 s)
  • Chat transition: non-persisted [child] returned control to [parent] line

File: _vendor/github.com/docker/docker-agent/docs/features/tui/index.md

Model providers and config fields (docker/docker-agent#3341, #3343, #3358, #3361, #3368, #3369, #3376, #3384, #3385, #3337, #3389, #3335, #3338, #3390)

  • New content/manuals/ai/docker-agent/model-providers.md: documents twelve new provider aliases (Baseten, Cerebras, Cloudflare AI Gateway, Cloudflare Workers AI, DeepSeek, Fireworks AI, Groq, Moonshot AI, OpenRouter, OVHcloud, Together AI, Vercel)
  • New content/manuals/ai/docker-agent/reference/config.md: documents compaction_model, bypass_models_gateway, and tags fields

@aheritier aheritier requested a review from dvdksn as a code owner July 2, 2026 04:08
@netlify

netlify Bot commented Jul 2, 2026

Copy link
Copy Markdown

Deploy Preview for docsdocker failed. Why did it fail? →

Name Link
🔨 Latest commit 0c8afc5
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6a546581fa73490008559f6e

@docker-agent docker-agent left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 docker-agent left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[LOW] NOTE callout may confuse readers about compaction behavior

The NOTE describes two scenarios without clearly distinguishing them:

  1. "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.)
  2. "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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[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_model to 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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[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 explicit token_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 explicit token_key — not the gateway's token.

@Sayt-0

Sayt-0 commented Jul 3, 2026

Copy link
Copy Markdown
Member

Since #25480, content/manuals/ai/docker-agent/ is mounted from the docker/docker-agent Hugo module and the two files edited here (model-providers.md, reference/config.md) no longer exist as hand-authored pages; they were replaced by mounted equivalents sourced from docker/docker-agent/docs/.

The content of this PR is already covered upstream:

This PR Upstream (docker/docker-agent)
12 new provider sections docs/providers/<provider>/index.md (one page per provider) + alias table in docs/providers/overview/
compaction_model docs/configuration/models/index.md, "Delegating Session Compaction"
bypass_models_gateway docs/configuration/models/index.md, "Gateway Bypass"
metadata version / tags docs/configuration/overview/index.md, metadata table

The pages will appear on docs.docker.com with the next version-pin bump (sync-docker-agent-docs.yml). This PR can be closed; future Docker Agent doc changes should target docker/docker-agent/docs/.

…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
@github-actions github-actions Bot added the dependencies Vendoring, packaging updates label Jul 13, 2026
@aheritier aheritier changed the title docs(docker-agent): add new model providers and config fields docs(docker-agent): update TUI docs and add model providers/config fields Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ai dependencies Vendoring, packaging updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants