<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Co-authored-by: erikengervall <5392475+erikengervall@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Document `sbx mcp unload` for removing a server from a running sandbox
without restarting the agent. Explain how to reload it, distinguish
unloading from removing its registration, and describe what happens
after unloading all static servers.
Validation: Markdown and style checks pass.
Generated by Codex.
## Description
Updates the [custom role permissions
reference](https://docs.docker.com/security/roles-and-permissions/custom-roles/permissions-reference/)
to match the permissions available when creating a custom role:
- **Licensing (new section):** "Manage licenses" lets a custom role
assign and revoke member licenses and manage auto-assign rules without
org ownership. It doesn't include purchasing or changing the number of
licenses. Added in docker/iam-services#1173 (BILL-5010).
- **DHI:** adds "Manage customizations", which was available in custom
roles but missing from the reference.
- **Cloud Sandboxes (new section):** adds "Use Cloud Sandboxes" (renamed
from "Use sandboxes" in docker/iam-services#1172).
Names and descriptions match `custom-role-metadata.yaml` in
iam-services. The page description, keywords, and intro are updated to
list the new areas.
## Draft until
- [ ] docker/iam-services#1173 is merged and deployed, so the Licensing
permission is visible in the custom roles UI.
## Related issues or tickets
- BILL-5010
- docker/iam-services#1173
- docker/iam-services#1172🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
## Summary
Adds links from each unit in the Top up your plan table on the
subscription and billing overview to the docs that cover managing that
entitlement (seats, licenses, Build Cloud minutes, DHI repositories, and
consuming domains).
Generated by Cursor
Made with [Cursor](https://cursor.com)
Co-authored-by: Cursor <cursoragent@cursor.com>
Short link for the Harbor + Docker Sandboxes integration, used in
Harbor's docs. Points to the launch blog until a docs page exists.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
<!--Delete sections as needed -->
## Description
Noted that DAP applies the open policy to new sandboxes by default,
which differs from local sandboxes.
## Related issues or tickets
DAPSS-889
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
## Description
The Mistral guide uses a v2 `spec.yaml` and injects credentials only for
`api.mistral.ai`. Update it to a v3 workload descriptor and companion
Dockerfile, with a pinned Vibe 2.25.8 installation and credential
injection for the inference, account, and managed-config hosts.
Keep the build-and-run walkthrough and add a FastAPI repair exercise
using the published community kit. Include three screenshots showing the
credential placeholder, Vibe's repair summary, and the model menu.
Readers verify the repair with pytest inside the sandbox and a Git diff
from the host repository.
## Validation
- Formatted and linted the changed guide with repository-pinned rumdl
and `scripts/lint.sh`: zero errors, warnings, or suggestions
- Validated the embedded descriptor against the upstream v3 JSON schema
and checked the three literal network hosts and authorization mappings
- Checked front matter, internal links, screenshot paths, and the public
sample configuration
- Ran fresh Gemini reader and technical reviews through Pi in SBX, with
tools, skills, and prior context disabled; fixed the findings and
received final READABLE and PASS verdicts
- Screenshots are from the interactive Vibe 2.25.8 sample; the earlier
sample run used sbx 0.46.0-rc5
Full Docker-based site validation and a rebuild of the tutorial kit
remain pending: the host Docker engine was unavailable. Schema and prose
checks do not establish image-build or runtime success.
## Reviews
- [x] Technical review through Gemini, plus descriptor schema validation
- [x] Editorial review through Gemini and local prose/lint checks
- [ ] Product review
---------
Signed-off-by: Oleg Šelajev <shelajev@gmail.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Co-authored-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
The API reference layout loaded Redoc from the `latest` CDN URL, which
now serves Redoc 3.0.0. That bundle is an ES module that uses
import.meta, so the classic script tag fails with "Cannot use
'import.meta' outside a module" and the Engine, Hub, and Registry API
pages render blank. Pin to the 2.x UMD build.
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
## Description
Built-in agent names select v2 kits, while published v3 workloads such
as `sbx/claude` collide with those names. This change recommends v3,
maps built-in agents to published v3 workloads with distinct names, and
shows compatible CLI, kit set, and environment-file examples. The
environment-file guide starts with a built-in v2 agent and links to a
separate v3 workflow.
Compatibility, capability requirements, and migration steps each live on
the page where readers need them.
Scoped Markdown and Vale checks pass. OCI manifests verify the v2
Playwright mixin and the published v3 references; v0.48.0
agent-registration and environment kit-resolution tests pass. A full
sandbox launch was unavailable because Docker sign-in is required in
this workspace.
@netlify /ai/sandboxes/customize/use-kits/
Generated by Codex
The Console getting started page ended at sandbox launch. Expand it into
a complete first session: review a public sample project with Claude
Code, inspect and save the result, optionally connect VS Code or Cursor
over SSH, and pause or delete the sandbox.
Preserves the sandbox options reference and existing heading anchors.
The platform overview remains the gateway to concepts; use-case guides
remain separate in #26321.
Formatting, scoped Markdown and Vale lint, Hugo build, and all 19
internal links passed. This remains a draft pending live Console, cloud
SSH, and editor verification.
@netlify /agentic-platform/get-started/
[Preview the
walkthrough](https://deploy-preview-26339--docsdocker.netlify.app/agentic-platform/get-started/)
Generated by Codex
## Summary
Update the Sandbox documentation for the v0.48.0 CLI refactor: renamed
flags, settings commands, terminal output, structured output, and
non-interactive confirmations. Add a migration reference for scripts and
CI workflows, with a [**Copy as prompt**
button](https://deploy-preview-26314--docsdocker.netlify.app/ai/sandboxes/workflows/automation/#update-scripts-for-v0480)
that copies agent instructions and the section Markdown.
This PR targets `main` independently of the other PRs in the sbx/v0.48.0
milestone. It keeps the generated reference import separate from
documentation edits:
- Vendor the 120 generated CLI YAML files
- Update command examples and guidance. Historical release notes retain
their original command spellings.
The other milestone PRs cover separate release features; this PR covers
the CLI migration.
@netlify /ai/sandboxes/workflows/automation/
Generated by Codex
Several sandbox feature guides omit supported tasks or describe them
inaccurately. This change fills those gaps in the documentation for
released Sandboxes v0.47.0 and organizes the additions around the tasks
readers need to complete.
- MCP: document DHI registration after the other server inputs, make
OAuth client changes a focused maintenance task, and place resource
overrides after normal OAuth setup.
- Environment files: consolidate file placement and write protection
after the first setup example, and explain plan output before listing
its symbols.
- Cloud: separate saving and reusing templates, importing local
templates, and customizing with kits. Explain capture modes beside the
relevant operations.
- Skills: correct import precedence, include OpenCode, and explain
skipped linked dependencies after the import command.
- Kits v2: correct the downloaded archive formats in the command entry
and put provenance inspection with signing and verification. Omit OCI
storage details that don't help complete these tasks.
Behavior was checked against the v0.47.0 source. In particular,
replacing an OAuth client secret does not clear its previous identity
binding; the recovery task retains the required reset and tells readers
to verify the intended client and provider first.
Validation: scoped Markdown and Vale lint passed, the full Hugo
development build passed, and checks of the five rendered guides
confirmed complete code blocks, visible placeholders, plan indentation,
valid same-page anchors, skills import order, and the revised task
headings. Changes are committed separately by issue. The v0.48 migration
remains in #26314.
```release-note
NONE
```
---------
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
## Summary
The v2 kit reference says that adding a kit with startup commands
requires removing and recreating the sandbox. Document support for
startup commands through `sbx kit add` and explain when they run.
Implementation:
[docker/sandboxes#6886](https://github.com/docker/sandboxes/pull/6886).
Checked against the `release/v0.48` source and its regression coverage.
Changed Markdown passes rumdl and Vale.
For [Sandboxes
v0.48.0](https://github.com/docker/sandboxes/issues/7014); kept in draft
for the upcoming release.
@netlify /ai/sandboxes/customize/kits-v2/
Generated by Codex
Add a kit capability support reference showing local and cloud
availability, minimum `sbx` versions, capability-group behavior, and
restrictions on `sbx kit add`. Link it from the authoring overview and
clarify that v3 kits must request SSH-agent forwarding. Keep capability
definitions and examples in the upstream specification.
Validation: Markdown and style checks pass; upstream capability links
verified.
Generated by Codex.
Document the Windows SSH-agent fallback under `ssh.agentSocketPath`,
including what happens when both the setting and `SSH_AUTH_SOCK` are
unset. Keep the general SSH-agent guide focused on setup and linked to
the settings reference.
Validation: Markdown and style checks pass.
Generated by Codex.
Document how to select a model reasoning level with `sbx run --variant`,
with an example and the relevant agent limitations.
Validation: Markdown and style checks pass.
Generated by Codex.
Document desktop app connections that create a sandbox on first use and
reuse it on later connections. Keep the shared setup and lifecycle
behavior on the integrations overview, with brief links from the ChatGPT
and Claude Desktop pages.
Validation: Markdown and style checks pass.
Generated by Codex.
Document using stored API keys for hosted and custom model providers.
Explain how the host proxy supplies the key to the model service and
make clear that selecting a provider does not restrict the key to that
provider's endpoint. Clarify the environment-variable fallback.
Validation: Markdown and style checks pass.
Generated by Codex.
Document expiration settings for cloud moves and environments, including
automatic restart at expiration. Organize the cloud environment guidance
into task sections covering setup, supported settings, expiration,
credentials, reuse, removal, and recovery.
Validation: Markdown and style checks pass.
Generated by Codex.
## Summary
Kit authors can use `SBX_AGENT` to choose setup behavior for the
provisioned agent. Document the value for built-in and custom agents,
and how install hooks request the variable.
Implementation:
[docker/sandboxes#6876](https://github.com/docker/sandboxes/pull/6876).
Checked against the `release/v0.48` source and its regression coverage.
Changed Markdown passes rumdl and Vale.
For [Sandboxes
v0.48.0](https://github.com/docker/sandboxes/issues/7014); kept in draft
for the upcoming release.
@netlify
/ai/sandboxes/customize/author/#pass-environment-variables-to-hooks
Generated by Codex
## Summary
The build policy docs covered HTTP downloads through `ADD` but did not
explain how to block URLs requested by `RUN` steps. Add a tested
allowlist example using `"caps": {"exec.proxy": true}` in the policy
file and update the HTTP input reference, with a brief builder flag
example for CI.
Verified that Debian package downloads pass and the blocked URL returns
HTTP 403 and fails the build. Scoped Markdown and Vale checks passed,
with one existing Vale warning on unchanged text.
@netlify /build/policies/usage/
Generated by Codex
## Summary
Removes files left over from earlier agent tooling that nothing
references anymore, and moves the `curate-whats-new` examples next to
the skill that uses them.
- Delete `tech_writer.yml` and `docs_engineer.yml`, unused docker-agent
configs, and the `.validation.log` ignore entry that only they wrote.
- Delete `.github/prompts/`, unreferenced Copilot prompt files that link
to a nonexistent style guide.
- Move `.github/agents/whats-new-examples/` to
`.agents/skills/curate-whats-new/examples/`.
`.github/agents/docs-scanner.yaml` and the `docker-agent-action`
workflows stay, since CI still uses them.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
## Summary
Remove experimental badges and notices for the Cloud Sandboxes CLI, API,
and SDK, including the API reference card and CLI release notes.
Preserve the Docker Agentic Platform experimental status, the
subscription requirement, and feature-specific experimental warnings.
@netlify /ai/sandboxes/cloud/
Generated by Codex
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Signed-off-by: aevesdocker <allie.sadler@docker.com>
## Summary
Gordon's Supplemental Terms are no longer in effect. Replace the
reference under Questions about privacy with a link to the Docker
Subscription Service Agreement.
@netlify /ai/gordon/concepts/data-privacy/
Generated by Codex
Closes#26138
The `get` example under Extensions SDK backend API is missing its
closing parenthesis, so copying it into an extension gives a syntax
error before anything runs:
```typescript
ddClient.extension.vm.service
.get("/some/service")
.then((value: any) => console.log(value)
```
Every other example on the same page closes with `console.log(value));`,
so this matches that rather than only adding the bracket.
David Karlsson
Greg MondelloandClaude Opus 5.5
Sebastiaan van Stijn
Mathieu Champlon
Sohan PatilandClaude Opus 5.5
Paweł Gronowski
Craig Osterhout
Oleg ŠelajevandDavid Karlsson
Usha MandyaandClaude Opus 5.5
Mark HandClaude Opus 5.5
Allie Sadler
Sweta Sahoo
mrchatam