## Description
Standardizes the terminology used to describe Gordon’s free tier across
the documentation.
- Replaces **“Personal (free) subscription”** with **“Base tier
(free)”** in the Gordon data privacy documentation.
- Aligns the terminology with the existing Gordon usage-limits
documentation.
- Preserves the existing data retention policy and all related
explanations.
This change improves consistency and clarity for readers without
changing the documented data privacy practices.
## Related issues or tickets
Closes#26419
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--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
The Git workflow guide omitted mountless repositories and suggested that
separate branches were enough to isolate simultaneous tasks. Add a
mountless workflow, compare where changes appear, clarify Git access in
direct mode, and align the workflows overview and Claude Code guidance
on using separate working directories.
Markdown and Vale checks pass for all three changed pages.
@netlify /ai/sandboxes/workflows/git/
Generated by Codex
## Description
Make the first Docker Agentic Platform session useful without a model
provider API key: launch the Shell kit, clone the Welcome to Docker
sample, build its container image, run the app, and preview it through
the Console's port connection. Readers can continue editing the same
project in VS Code or Cursor over SSH.
PReview:
https://deploy-preview-26413--docsdocker.netlify.app/agentic-platform/get-started/
## Summary
The cloud environment example didn't show how to work on a project, and
readers had to reach later subsections to discover the differences from
local sandboxes. Move the walkthrough into the cloud section, explain
those differences upfront, and show how to create an environment, copy
in a project, work with Claude Code, retrieve changes, and clean up.
Cover cloud credentials, expiration, unsupported settings, and reuse
limitations. Preserve the original entry anchor and update cloud
cross-references. Behavior checked against docker/sandboxes
release/v0.49 at c5b19951af12; scoped Markdown and Vale checks, Hugo
build, and rendered internal link checks passed. No live cloud session
was run.
@netlify /ai/sandboxes/cloud/environment-files/
Generated by Codex
Environment files were introduced mainly as an alternative to publishing
a kit set, leaving their broader role unclear. Explain near the top of
both pages how kits package software and its requirements while
environment files capture sandbox configuration, add reciprocal links,
and shorten the kit-set comparison.
Scoped rumdl and Vale checks pass for both changed pages.
@netlify /ai/sandboxes/customize/
Generated by Codex
Refresh on top billing docs :)
TO DO:
Confirm Docker Offload situation
Remove random link to Testcontainers (?)
Review that Manage your plans h2 lol
Co-authored-by: Cursor <cursoragent@cursor.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>
Cached template images and existing sandboxes need updates after the external eMudhra certificate authority compromise. Add guidance for recreating sandboxes with refreshed images or updating CA certificates in place.
Full template contents and T3 prerequisites did not reflect the included C/C++ toolchain. Document the tools and make manual installation conditional on missing dependencies.
Environment merging guidance could imply a later override repairs invalid input. Explain that every source file, including user defaults, must be valid before merging.
The automation guide did not identify quiet output for policies, settings, or approvals. List the returned identifiers and distinguish cloud policy output.
Automation guidance did not cover secret removals that match no stored entry. Explain the nonzero result and checking for matching secrets before cleanup.
Proxy guidance excluded host connections to cloud sandboxes. Document their proxy scope and the direct cloud SSH setting, and link the cloud SSH workflow to that guidance.
Git workflows did not explain how host ignore decisions reach local sandboxes. Document the creation-time snapshot and its limits without implying that ignored files are inaccessible.
The integration guide suggested SSH shells might start outside the primary workspace. State that interactive SSH starts in the sandbox workspace while editor folder pickers can choose another location.
The signing instructions did not account for Git changing signed file contents. Explain the signing warning and why local verification does not establish that committed bytes match.
Kit authors lacked guidance for checking local sources without a daemon or sign-in. Document offline validation and inspection, including the policy checks they skip.
## Description
Orca is an agent development environment that runs coding agents in
parallel,
each in its own git worktree. It connects to a sandbox as a plain SSH
host and
installs its own relay inside it, so this works today with no changes on
either
side, and nothing documents it yet.
The page covers the SSH target fields (including the `_default_user_`
username), the C++ compiler Orca's remote terminals need, how agent
selection
works, and credential injection. It follows the shape of the T3 Code
page.
A separate change adds a C/C++ toolchain to the full sandbox templates.
Template
images publish independently of an `sbx` release, so the manual install
here
stops being necessary as soon as the new images carry the toolchain, and
I'll
follow up to drop it once I can pull one that does.
The T3 Code page gets the same one-line change, since it documents the
same
manual install and should name the same package.
Left out deliberately: Orca also offers an "Orca-managed Node" runtime
per SSH
target, which uploads its own Node and needs no compiler at all. I have
not
tested that path against a sandbox, so it stays out until I have.
## Related issues or tickets
- https://github.com/stablyai/orca/issues/13665
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Signed-off-by: Manuel de la Peña <manuel.delapena@docker.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
## Summary
Replace the two JIT sign-in diagrams with one Mermaid flowchart, and
retitle the sections so setup, disable, and re-enable are distinct
tasks.
Agent readiness scores increased to 98, up from 94 for the live doc.
@netlify /security/provisioning/just-in-time/
Preview:
https://deploy-preview-26370--docsdocker.netlify.app/security/provisioning/just-in-time/
Generated by Cursor Grok
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
<!--Delete sections as needed -->
## Description
Adds a Mac troubleshooting topic for containers that can reach the
internet but not devices on the local network (LAN). The cause is Docker
Desktop not having the macOS **Local Network** permission: macOS then
blocks container traffic to devices on the local network, including the
router, while internet traffic still works. The fix is turning on Docker
in **System Settings** > **Privacy & Security** > **Local Network**,
which takes effect immediately, without restarting Docker Desktop.
Also adds a short **Local Network permission** section to the Mac
permission requirements page that links to the new topic, since that
page didn't mention it.
**Verified** on macOS 26.7 / Docker Desktop 4.92.0 by toggling Local
Network for Docker:
- Off: containers couldn't reach LAN peers or the default gateway (ping,
TCP, UDP DNS), while the internet and `docker pull` kept working.
- On: access came back immediately, on the same backend process, without
restarting Docker Desktop.
- **On a fresh install, macOS prompts for the Local Network permission,
so users who hit this have most likely denied that prompt at some
point.**
## Related issues or tickets
- https://github.com/docker/desktop-feedback/issues/636
## Reviews
- [ ] Technical review @mat007
- [ ] Editorial review
- [ ] Product review
---------
Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
## Description
Fixes#26385.
Correct the incomplete sentence in the Compose variable interpolation
guide so the relationship between `.env` variables and container
environment variables is clear.
## Validation
- `git diff --check`
- Scoped repository lint was unavailable because the pinned local
dependencies are not installed.
## Summary
Custom secret injection is limited to HTTP request headers, but the
credentials page recommended it for secrets in request bodies and
described replacement anywhere in a request. Remove that use case and
clarify the header-only restriction.
@netlify /ai/sandboxes/configuration/credentials/
Generated by Codex
## Description
Explain how the generated Kits section points agents to each kit's
guidance, including packaged context files under
`/usr/share/sandbox/kit/<stem>/` and the location of inline
instructions.
@netlify /ai/sandboxes/customize/use-kits/
Generated by Codex
<!--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>
<!--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>
