Add Docker Sandboxes integration page#355
Conversation
Documents the kernel/docker-sbx-kit mixin: how to install, what it provides (CLI, skills, proxy-managed Kernel API auth), how to load the kit, troubleshooting, and how it relies on the sbx proxy to keep KERNEL_API_KEY off the sandbox VM.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Strip duplicated kit/sbx mechanics (loading methods, spec breakdown, generic troubleshooting, validation commands) and route those to Docker's docs and the kit README. Keeps only what's unique to the Kernel integration: the kit's value prop, proxy-managed KERNEL_API_KEY, and the quickstart command. Reduces drift risk as Docker evolves sbx.
There was a problem hiding this comment.
Stale comment
Risk assessment: Very Low
This synchronized diff is limited to documentation and Mintlify navigation: it adds
integrations/docker-sandboxes.mdx, adds that page todocs.json, and links it fromintegrations/overview.mdx. I found no production codepaths, runtime behavior, infrastructure, auth/permissions logic, schema changes, prompts used for model behavior, or shared systems modified.The PR is already approved, so I’m not adding a duplicate approval. I also found no
CODEOWNERSfile in the repository, so there doesn't appear to be a code owner review requirement blocking the existing approval.Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Stale comment
Risk assessment: Very Low
The current diff is limited to documentation and Mintlify navigation: it adds
integrations/docker-sandboxes.mdx, adds that page todocs.json, and links it fromintegrations/overview.mdx. I found no production codepaths, runtime behavior, infrastructure, auth/permissions logic, schema changes, shared systems, or model prompt/instruction files modified.The PR is already approved, so I’m not adding another approval. I also found no
CODEOWNERSfile in the repository, so there doesn't appear to be a code owner review requirement blocking approval.Sent by Cursor Automation: Assign PR reviewers
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: PR only adds documentation (new .mdx files and updates to docs.json) with no changes to API endpoints or Temporal workflows. To monitor this PR anyway, reply with |
There was a problem hiding this comment.
Stale comment
Risk assessment: Very Low
The current diff is limited to documentation and Mintlify navigation: it adds
integrations/docker-sandboxes.mdx, adds that page todocs.json, and links it fromintegrations/overview.mdx. I found no production codepaths, runtime behavior, infrastructure, auth/permissions logic, schema changes, shared systems, or model prompt/instruction files modified.The PR is already approved, so I’m not adding another approval. I also found no
CODEOWNERSfile in the repository, so there doesn't appear to be a code owner review requirement blocking approval.Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Stale comment
Risk assessment: Very Low
The current diff is limited to documentation and Mintlify navigation: it adds
integrations/docker-sandboxes.mdx, registers that page indocs.json, and links it fromintegrations/overview.mdx. I found no production codepaths, runtime behavior, infrastructure, auth/permissions logic, schema changes, shared systems, or model prompt/instruction files modified.The PR is already approved, so I’m not adding a duplicate approval. I also found no
CODEOWNERSfile in the repository, so there doesn't appear to be a code owner review requirement blocking the existing approval.Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 42443ca. Configure here.
| The [Kernel kit](https://github.com/kernel/docker-sbx-kit) is a [Docker Sandboxes](https://docs.docker.com/ai/sandboxes/) [mixin](https://docs.docker.com/ai/sandboxes/customize/kits/) that gives any `sbx` agent: | ||
|
|
||
| - **Kernel CLI** (`@onkernel/cli`) installed at sandbox creation | ||
| - **Kernel agent skills** from [`kernel/skills`](https://github.com/kernel/skills), so Claude Code (and any agent that reads `~/.agents/skills`) can drive Kernel without prompting |
There was a problem hiding this comment.
Specific third-party AI product names used in docs
Medium Severity
The new page references "Claude Code" on line 9 and "Claude" on lines 26 and 42. Per project rules, documentation must not reference specific third-party AI products by name — generic, vendor-neutral terms like "a coding agent," "the agent," or "your AI tool" are expected instead. "Claude Code" is explicitly called out as an example of a term to avoid.
Additional Locations (2)
Triggered by learned rule: Use generic terms instead of specific third-party AI product names
Reviewed by Cursor Bugbot for commit 42443ca. Configure here.
Co-Authored-By: Claude Opus 4.7 <[email protected]>
There was a problem hiding this comment.
Stale comment
Risk assessment: Very Low
The current diff is limited to documentation and Mintlify navigation: it adds
integrations/docker-sandboxes.mdx, registers that page indocs.json, and links it fromintegrations/overview.mdx. I found no production codepaths, runtime behavior, infrastructure, auth/permissions logic, schema changes, shared systems, or model prompt/instruction files modified.The PR is already approved, so I’m not adding a duplicate approval. Since the synchronized update only corrected a documentation link and did not increase risk, I’m also not dismissing the existing approval. I found no
CODEOWNERSfile in the repository, so there doesn't appear to be a code owner review requirement blocking approval.Sent by Cursor Automation: Assign PR reviewers
Co-Authored-By: Claude Opus 4.7 <[email protected]>
There was a problem hiding this comment.
Risk assessment: Very Low
The latest diff remains limited to documentation and Mintlify navigation: it adds integrations/docker-sandboxes.mdx, registers that page in docs.json, and links it from integrations/overview.mdx. I found no production codepaths, runtime behavior, infrastructure, auth/permissions logic, schema changes, shared systems, or model prompt/instruction files modified.
The PR is already approved, so I’m not adding a duplicate approval. The new synchronized update only changes documentation wording and does not increase risk, so I’m also not dismissing the existing approval. I found no CODEOWNERS file in the repository, so there doesn't appear to be a code owner review requirement blocking approval.
Sent by Cursor Automation: Assign PR reviewers
dprevoznik
left a comment
There was a problem hiding this comment.
LGTM - made a few small changes, feel free to revert




Summary
integrations/docker-sandboxes.mdxdocumenting thekernel/docker-sbx-kitmixin for Docker Sandboxes (sbx).KERNEL_API_KEY), validation, and troubleshooting.docs.jsonnavigation and theintegrations/overview.mdxindex.Why
Surface the new sbx kit as a first-class integration so users can run agents inside isolated Docker sandboxes against Kernel without exposing their API key to the agent.
Test plan
mintlify devlocally and confirm the new page renders, sidebar entry shows under Integrations, and all internal links resolve.Note
Low Risk
Low risk: documentation-only changes that add a new integration page and navigation links, with no runtime or API behavior changes.
Overview
Adds a new
integrations/docker-sandboxes.mdxguide documenting thekernel/docker-sbx-kitmixin for runningsbxagents with Kernel CLI/skills and proxy-managedKERNEL_API_KEY.Updates Mintlify navigation (
docs.json) and the integrations index (integrations/overview.mdx) to surface the new Docker Sandboxes integration link.Reviewed by Cursor Bugbot for commit 90857c6. Bugbot is set up for automated code reviews on this repo. Configure here.