## Summary
Agents can produce prose that passes style checks but still sounds
unnatural or takes effort to understand. Add guidance to AGENTS.md and a
required prose review with concrete examples to the write skill.
Broaden the skill to cover PR text, release notes, and other prose,
while keeping its branch and commit workflow specific to documentation
fixes.
Markdown formatting passes. Vale reports only existing findings in
unchanged text; the skill validator rejects the existing `hooks` field.
Generated by Codex
The vendored Sandboxes 0.42.0 release notes omitted CVE-2026-77179 and CVE-2026-79994. Re-vendor the updated upstream release notes to include both fixes in a dedicated Security section.
@netlify /reference/api/
[Preview the API
reference](https://deploy-preview-26048--docsdocker.netlify.app/reference/api/)
Adds a shared API reference experience for Hub, DVP, and Registry: a
catalog, operation navigation, linked schemas, request and response
examples, and matching HTML and Markdown output. A validation and
generation pipeline prepares the reference data for Hugo and runs as
part of Docker and Netlify builds.
Migrates the three specifications to OpenAPI 3.2, correcting response
shapes, nullable fields, and authentication and token examples. The Hub
migration also corrects SCIM contracts and CSV exports; DVP gains
complete report response schemas and examples. Registry keeps its
documented Hub-specific subset, with authentication and media
negotiation expressed through OpenAPI security and content fields.
Validation is strict for both checks and generation, with no exception
baseline or bypass flag. The build uses the migrated sources directly,
without migration scripts or records.
Page and specification URLs remain stable, including the DVP alias.
Operation and schema anchors change. Engine and Governance retain their
existing references.
Validated locally with Go tests, strict validation of all three
specifications (zero diagnostics), scoped formatting and lint, and a
full Hugo build checking all 176 HTML/Markdown page pairs, example
parity, reference links, and byte-identical published specifications. A
browser check confirmed raw CSV rendering and the generated request
header. No live API requests were made.
The template cache description omitted the default registry refresh, and users had no guidance for updating installed agents. Correct the cache behavior and explain generic agent updates and their persistence boundary.
Custom images without socat cannot create the forwarded SSH agent socket even when SSH_AUTH_SOCK is set. Document the dependency and link to forwarding settings for other failures.
Nested build containers do not inherit the sandbox certificate store. Add a Dockerfile example that installs the proxy CA, passes build proxy settings, and accounts for an additional organization CA.
The Sandboxes environment-file and kit references narrate routine validation checks that add little value for readers.
Remove redundant validation prose and express kit schema migration as a reader action while retaining configuration constraints and defaults.
The Locked Down description implied that only user-added rules could grant access, overlooking built-in agent kit allowances. Explain preset initialization, show kit-rule inspection, and demonstrate an explicit deny.
The sandbox docs did not describe image attachments for Claude Code. Add a release-note entry and a short explanation of pasting or dropping an image into the terminal before sending a prompt.
The Sandboxes guides omitted custom MCP request headers, didn't explain
the MCP secrets shown by `sbx secret ls`, and described older OAuth
discovery and scope-selection behavior.
Document API-key setup, host-only MCP credentials, managed endpoint
records, rotation, restart requirements, and removal. Correct OAuth
client-secret naming and explain migration from the older spelling.
Cover the advertised common OIDC scope fallback, non-blocking scope
warnings, and `--skip-ssrf-check` for private OAuth metadata discovery
and redirects, as backported in docker/sandboxes#6079.
Markdown and Vale checks pass for the changed pages.
@netlify /ai/sandboxes/mcp-gateway/
Generated by Codex
The registry credentials guide omits `--registry-auth-endpoint`. Add a
self-hosted GitLab example and explain the exact HTTPS host and path
trusted to receive the registry credential, URL restrictions, and
behavior without explicit configuration.
Validation: scoped rumdl and Vale checks pass with no issues.
@netlify /ai/sandboxes/configuration/credentials/
Generated by Codex
Document `sandboxOptions.skills` in `sbxenv.yaml`, including the `off`,
`readonly`, and `readwrite` modes and the daemon-resolved default for
sbx v0.43.0.
@netlify /ai/sandboxes/configuration/environment-files/
Generated by Codex
The usage guide shows only the legacy prune filter and does not explain why a sandbox created without attaching can stop before its first use.
Use the v0.43 until filter, describe its accepted values, and explain automatic stopping and reattachment after sbx create.
The v0.42 shorthand limitation interrupts the quick start for Kiro, Copilot, and Droid even though v0.43.0 restores launching them by name. Remove the three callouts and preserve the affected-version guidance and full kit workarounds in troubleshooting.
The Agentic Platform lifecycle guidance did not explicitly cover background processes. Clarify that all processes inside a sandbox stop when the sandbox stops.
Fetch the Docker style package from docs-toolkit and retain only the local vocabulary and repository-specific configuration. Resolve existing canonical-name violations exposed by the shared package.
## Description
Document GitHub Actions cache write restrictions that can cause cache
export to fail after a successful image push, including workflows
triggered when a pull request is merged into the default branch. Explain
how to restore cache in read-only workflows and populate it from a
workflow with write access.
Clarify how `cache-mode` overrides affect access and why
`ignore-error=true` suppresses export failures without fixing denied
writes.
## Related issues or tickets
closes https://github.com/docker/build-push-action/issues/1571
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
The Docker Sandboxes release notes do not include the v0.42.0 stable release.
Regenerate the release list from docker/sbx-releases and retain the latest three minor release lines.
Co-Authored-By: Codex <noreply@openai.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Summary
Expand Docker's local Vale style with documented direct-language
substitutions and focused checks for marketing copy and meta-commentary.
Remove stale style-guide links and clarify how agents should review
scoped Vale output.
Generated by Codex
## Summary
Prototypes a task-first Get started experience organized around three
short journeys:
- Containerization: run a container and application stack, build an
image, and share it.
- AI development: move an existing full-autonomy coding-agent workflow
into a disposable Docker Sandbox.
- Administration: invite a pilot user, apply a Docker Desktop policy,
and verify the managed experience.
The change replaces the existing Get started landing content with a
compact journey selector, adds direct installation paths for Docker and
Docker Sandboxes above the tutorials, adds the tutorials as a
collapsible sidebar group, and updates homepage and `llms.txt` discovery
paths. The container and sandbox tutorials include focused next steps
into relevant concept and manual pages.
The superseded Introduction series and its unused images are removed.
Its published routes and legacy aliases, including the workshop routes
consolidated on `main`, redirect to the replacement container tutorial
or the Get Docker page. Inbound documentation links point to the new
tutorial.
The existing Docker concepts content remains available while this
direction is evaluated.
@netlify /get-started/
## Deploy preview
- [Get started landing
page](https://deploy-preview-25986--docsdocker.netlify.app/get-started/)
- [Containerization
tutorial](https://deploy-preview-25986--docsdocker.netlify.app/get-started/tutorials/run-an-app/)
- [AI agent
tutorial](https://deploy-preview-25986--docsdocker.netlify.app/get-started/tutorials/run-an-agent/)
- [Administrator
tutorial](https://deploy-preview-25986--docsdocker.netlify.app/get-started/tutorials/admin-set-up/)
Generated by Codex
---------
Co-authored-by: Codex <noreply@openai.com>
## Summary
Add Devin as a built-in agent with interactive sign-in and reusable,
proxy-managed authentication.
@netlify /ai/sandboxes/agents/
Generated by Codex
---------
Co-authored-by: Codex <noreply@openai.com>
## Summary
Documents the v0.42.0 workspace behavior for Docker Sandboxes: `sbx run`
continues to mount the current directory when no path is provided, while
`sbx create` accepts zero workspace paths and creates a mountless
sandbox when they are omitted.
Explains the mountless working directory and persistence model, keeps
explicit paths where a project workspace is load-bearing, uses named
attachment for existing sandboxes, and adds troubleshooting for
sandboxes created without project files.
The generated CLI reference will receive the matching upstream help text
when v0.42.0 is vendored.
Closesdocker/sbx-releases#466
Generated by Codex
---------
Co-authored-by: Codex <noreply@openai.com>
## Summary
Document the per-user and machine-wide Windows MSI install scopes,
including their install locations and PATH changes. Add the silent
administrator install command and the verified machine-upgrade reboot
caveat for Docker Sandboxes v0.42.
@netlify /ai/sandboxes/install/
## Preview
[Install Docker
Sandboxes](https://deploy-preview-25948--docsdocker.netlify.app/ai/sandboxes/install/)
Generated by Codex
Co-authored-by: Codex <noreply@openai.com>
## Summary
Document how to add, list, update, and remove repository-managed Docker
Sandbox skills introduced in Docker Sandboxes v0.42. Clarify how
repository-managed skills interact with host imports and the shared
skills store.
@netlify /ai/sandboxes/workflows/agent-skills/
[Preview the agent skills
workflow](https://deploy-preview-25910--docsdocker.netlify.app/ai/sandboxes/workflows/agent-skills/)
Generated by Codex
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Codex <noreply@openai.com>
## Summary
Document local sandbox clipboard writes as a bounded host integration in
the isolation documentation. Clarify that clipboard writes don't expose
existing clipboard text and that host clipboard image reads remain a
separate opt-in feature.
@netlify /ai/sandboxes/security/isolation/
[Preview the updated isolation
documentation](https://deploy-preview-25947--docsdocker.netlify.app/ai/sandboxes/security/isolation/)
Generated by Codex
---------
Co-authored-by: Codex <noreply@openai.com>
The checked-in sbx command reference predates the v0.42.0 release and omits or misstates its command surface.
Replace data/sbx_cli with the generated v0.42.0 reference while preserving the corrected private-network example from PR #26004.
Co-Authored-By: Codex <noreply@openai.com>
Several documented prose patterns were not enforced, and agents could overlook non-fatal Vale warnings.
Expand Docker's local Vale rules, remove obsolete rule links, and clarify scoped agent validation.
Governance monitoring did not explain the unresolved state shown when Docker cannot select one governing organization. Document the multiple-organization trigger, fail-closed behavior, and administrator escalation.
Co-Authored-By: Codex <noreply@openai.com>
The Agentic Platform docs omitted the agent-less Shell sandbox type and implied every sandbox needed a model credential.
Document the Shell environment, shared runtime details, compute sizing, and credential behavior.
Co-Authored-By: Claude <noreply@anthropic.com>
Marlin auto-captured installer links without stable labels matching the legacy Segment download events. Add explicit labels to installer buttons and release-note shortcodes, and route WSL users through the Windows installation guide.
Co-Authored-By: Claude <noreply@anthropic.com>
## Description
The GC policy example in
`content/manuals/build/cache/garbage-collection.md`
defines the first policy as:
> Find "stale" cache records that haven't been used in the past 48
hours, and
> delete records until there's maximum 5GB of "stale" cache left.
It then walks through a sweep over 11GB of cache (7GB stale, 4GB other)
and
concludes:
> A GC sweep would delete 5GB of stale cache as part of the 1st policy,
with a
> remainder of 6GB, meaning the 2nd policy does not need to clear any
more cache.
Both numbers contradict the policy as defined. Keeping a *maximum of
5GB* of
stale cache means deleting 2GB of the 7GB, which leaves 5GB stale plus
4GB
other, for 9GB in total.
The 6GB figure is internally consistent only with the opposite reading —
"delete 5GB of stale cache", leaving 2GB stale plus 4GB other. That
reading is
what the sentence asserts, and it is not what the policy says, so the
two
numbers are wrong together rather than independently.
The example's point survives the correction: 9GB is still under the
second
policy's 10GB limit, so the second policy does not need to clear any
more
cache.
```diff
-A GC sweep would delete 5GB of stale cache as part of the 1st policy, with a
-remainder of 6GB, meaning the 2nd policy does not need to clear any more cache.
+A GC sweep would delete 2GB of stale cache as part of the 1st policy, leaving
+9GB of cache in total, meaning the 2nd policy does not need to clear any more
+cache.
```
Note for the reporter of #25927: the "delete 2GB" half of the report is
right,
but the report also says the "remainder of 6GB" is correct. It isn't —
11GB minus 2GB is 9GB. 6GB only follows from the misreading being
corrected
here.
## Related issues or tickets
Fixes#25927
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01TGSfAZyRTEw9qGGzVECGYk
Signed-off-by: Sunmin Lee <134378502+sunm2n@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The FAQ did not explicitly state that Open is selected by default for every sandbox type. Clarify that Open permits all outbound destinations and list the options for restricting egress.
Co-Authored-By: Claude <noreply@anthropic.com>
Direct mounts authorize workspace access by path, so hard-linked files can expose writes outside the authorized root. Document the behavior and explain that clone mode mounts the primary host repository read-only.
Refs docker/sandboxes#4715
Co-Authored-By: Claude <noreply@anthropic.com>
The Agentic Platform docs did not list all credentials supported by the Secrets page. Add Groq and xAI to the provider references and record the update in the release notes.
Co-Authored-By: Codex <noreply@openai.com>
Automated crawlers had no dedicated trap route in the docs site. Add a hidden site-wide footer link to a noindex page whose existing Marlin pageview identifies requests.
Co-Authored-By: Codex <codex@openai.com>
The v0.42 release adds consent-based diagnostics uploads for selected daemon errors.
Document the prompt, setting, bundle handling, and distinction from manual uploads.
Co-Authored-By: Claude <noreply@anthropic.com>
## Summary
Remove the scheduled What's New curation workflow and its dedicated
agent configuration. Tune the retained skill for manual use: report
every selected entry explicitly, summarize retained and expired entries,
limit exclusion notes to credible candidates, and avoid
workflow-specific `.pr-body.md` files.
Generated by Codex
Co-authored-by: Claude <noreply@anthropic.com>
The scheduled curation workflow adds operational complexity to an editorial task that requires human review.
Remove the automation and tune the retained skill to report decisions directly without workflow-specific handoff files.
Co-Authored-By: Claude <noreply@anthropic.com>
The general AI ownership rule also covered sandbox governance documentation. Add a narrower rule assigning governance and audit log pages to Craig Osterhout.\n\nCo-Authored-By: Claude <noreply@anthropic.com>
The kit reference did not state that setup.files runs as the non-root agent user. Document the UID 1000 write restriction and direct root-owned path writes to setup.install.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Description
The sbxenv docs
[document](https://docs.docker.com/ai/sandboxes/sandbox-environments/#workspace)
the direct mount risks, mirroring them here for completeness.
## Related issues or tickets
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [x] Editorial review
- [x] Product review