Skip to content

Add Docker Sandboxes integration page#355

Open
guergabo wants to merge 7 commits into
mainfrom
hypeship/docker-sandboxes-integration
Open

Add Docker Sandboxes integration page#355
guergabo wants to merge 7 commits into
mainfrom
hypeship/docker-sandboxes-integration

Conversation

@guergabo
Copy link
Copy Markdown
Collaborator

@guergabo guergabo commented May 6, 2026

Summary

  • New integration page at integrations/docker-sandboxes.mdx documenting the kernel/docker-sbx-kit mixin for Docker Sandboxes (sbx).
  • Covers prerequisites, quickstart, kit loading methods, what the kit installs (CLI, skills, network allow-list, proxy-managed KERNEL_API_KEY), validation, and troubleshooting.
  • Adds the page to docs.json navigation and the integrations/overview.mdx index.

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

  • Run mintlify dev locally and confirm the new page renders, sidebar entry shows under Integrations, and all internal links resolve.
  • Verify external links (Docker docs, kit repo, dashboard, Anthropic console) point to the right places.

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.mdx guide documenting the kernel/docker-sbx-kit mixin for running sbx agents with Kernel CLI/skills and proxy-managed KERNEL_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.

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.
@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented May 6, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Kernel 🟢 Ready View Preview May 6, 2026, 7:42 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

guergabo added 2 commits May 6, 2026 20:04
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.
cursor[bot]
cursor Bot approved these changes May 6, 2026
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

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 to docs.json, and links it from integrations/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 CODEOWNERS file in the repository, so there doesn't appear to be a code owner review requirement blocking the existing approval.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

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 to 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 another approval. I also found no CODEOWNERS file in the repository, so there doesn't appear to be a code owner review requirement blocking approval.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@dprevoznik dprevoznik marked this pull request as ready for review May 12, 2026 01:31
@firetiger-agent
Copy link
Copy Markdown

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

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 @firetiger monitor this.

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

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 to 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 another approval. I also found no CODEOWNERS file in the repository, so there doesn't appear to be a code owner review requirement blocking approval.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

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 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. I also found no CODEOWNERS file in the repository, so there doesn't appear to be a code owner review requirement blocking the existing approval.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ 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
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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)
Fix in Cursor Fix in Web

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 <noreply@anthropic.com>
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

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 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. 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 CODEOWNERS file in the repository, so there doesn't appear to be a code owner review requirement blocking approval.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

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.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Copy link
Copy Markdown
Contributor

@dprevoznik dprevoznik left a comment

Choose a reason for hiding this comment

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

LGTM - made a few small changes, feel free to revert

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants