Skip to content
This repository was archived by the owner on Oct 7, 2026. It is now read-only.

feat(sandboxes): add DeepSeek Harness (dsh) sandbox image - #95

Closed
zac-wang-nv wants to merge 1 commit into
NVIDIA:mainfrom
zac-wang-nv:feat/dsh-sandbox
Closed

zac-wang-nv wants to merge 1 commit into
NVIDIA:mainfrom
zac-wang-nv:feat/dsh-sandbox

Conversation

@zac-wang-nv

Copy link
Copy Markdown

Summary

  • Adds sandboxes/dsh/: an OpenShell sandbox image for DeepSeek Harness (dsh), layered directly on sandboxes/base/ (no NemoClaw involved), matching the gemini/codex CLI-sandbox pattern already in this repo.
  • dsh's headless profile (one task in, final answer out, no server/open port) is the intended entrypoint for eval/scripted use — dsh --profile headless "<task>".
  • policy.yaml extends the base policy with a deepseek_harness network block (api.deepseek.com for the default deepseek-v4-flash provider, registry.npmjs.org for runtime dsh plugin install).
  • No workflow changes needed: build-sandboxes.yml's change-detection and build matrix are directory-driven (any sandboxes/<name>/Dockerfile), so this is picked up automatically.

Test plan

  • sandboxes/dsh/policy.yaml validated as well-formed YAML
  • CI: Build Sandbox Images workflow builds dsh against base (this PR)
  • Manual: openshell sandbox create --from dsh + dsh --profile headless "echo hello" once an image is published

🤖 Generated with Claude Code

Installs @deepseek-ai/dsh on the community base, matching the gemini/codex
pattern: a plain CLI layered on openshell-base with its own policy.yaml,
no gateway. dsh's headless profile (one-shot task in, final answer out, no
server, no open port) is the intended entrypoint for eval/scripted use, the
same shape as the other CLI-driven sandboxes here.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Signed-off-by: Zac Wang <zacw@nvidia.com>
@johntmyers johntmyers closed this Oct 7, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants