Enterprise: document the Sandbox Image option (Full or Slim)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 35/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- markdown
调研方向
Start in enterprise/vm-install/admin-console-configuration.mdx: find the Sandbox Configuration table and the existing Custom Sandbox Image subsection. The Full and Slim behavior is described in the issue, but the warm-sandbox and airgap details are marked to confirm, and the work is blocked on OpenHands-Cloud#1421. Done means a Sandbox Image row, a short section, a cross-link, and a release note, with the unconfirmed points checked against the shipped release.
由索引模型根据 Issue 内容生成。
描述
Summary
OpenHands Enterprise is adding a "Sandbox Image" option to the Admin Console that chooses between a full and a slim agent-server image. The Enterprise docs need to explain it.
What to document
- In
enterprise/vm-install/admin-console-configuration.mdx, add aSandbox Imagerow to the Sandbox Configuration table and a short section on the two choices.- Full: includes VS Code and the built-in ACP clients (Claude Code, Codex, Gemini CLI). It is the default, so existing installs keep their behavior.
- Slim: leaves out VS Code and the built-in ACP clients. Browser and Docker support are kept, and users won't see a VS Code tab.
- The option is hidden and ignored when
Use a Custom Sandbox Imageis on, because the custom image is used as written. - Say what happens to existing warm sandboxes and running conversations when the option changes (to confirm when it ships).
- Say which image airgap installs bundle (to confirm).
- Cross-link the existing "Custom Sandbox Image" subsection of the same page.
- Add a release note for the Enterprise version that ships the option.
Blocked on
OpenHands/OpenHands-Cloud#1421 and the enterprise change for the VS Code URL. Check the wording against the shipped release.
Tracking issue: https://github.com/OpenHands/enterprise/issues/835
This issue was drafted by an AI agent on behalf of the user.
- 主要语言
- MDX
- 星标
- 16
- 派生
- 82
- 平均合并
- 3 天 4 小时
- 30 天内合并 PR
- 75
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
OpenHands/docs 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
Docs: Child Conversations incorrectly implies the child's result is returned to the parent可能已有人在做 @sahithib20 于 8 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
Document SDK capability resolution and image-delivery contracts可能已有人在做 @neubig 于 5 天前认领。 未关闭
OpenHands/docs#976 · 已指派 1 人 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
awesome-dsh-plugin/awesome-dsh-plugin#9184 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
Lakr233/vphone-cli#738 ·
维护者通常 1 天内回复
-
[ordering-review] workshop order graph: 1 confirmed ordering problem, 3 cycles are false positives未关闭
难度 2/5 1-3 小时 新手友好度 78/100
githubnext/gh-aw-workshop#4943 ·
维护者通常 1 天内回复
-
Awaiting Triage
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100