feat: add DeepSeekHarnessAgent: DeepSeek Harness CLI runtime - #12
Open
now-ing wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DeepSeekHarnessAgent, a fourth built-inAgentimplementation backed by the non-interactivedsh --profile headless "<task>"command from DeepSeek Harness, alongside the existingCodexAgent,ClaudeAgent, andPiAgent.AgentOptions.sandboxmaps one-to-one onto theDSH_PERMISSION_MODEenvironment variable —read-only,workspace-write, anddanger-full-accessshare the shared policy names verbatim. Whensandboxis omitted, the variable is left untouched and DeepSeek Harness applies its ownworkspace-writedefault.AgentOptions.schemais embedded as a structured-output contract in the task (the headless app has no schema flag); the adapter parses the JSON object from the final assistant message, tolerating surrounding prose or Markdown fences.agent-default-modelsetting in$DSH_HOME/settings.yaml), soAgentOptions.modelandAgentOptions.additionalWritableDirectoriesthrow aTypeErrorinstead of being silently ignored. Session records persist under$DSH_HOMEfor audit; there is no ephemeral switch to fake.--agent dshselects the runtime fordeer-workflow create; usage/help strings, bilingual README + docs/api + docs/index + AGENTS.md, and the workflow-creator skill reference are updated.CodexAgentremains the defaultagent()export — purely additive and opt-in.Test plan
bun run typecheckbun run lintbun run format:checkbun test(100 pass, including 10 newDeepSeekHarnessAgenttests using a stub CLI and one newcreate --agent dshintegration test)DeepSeekHarnessAgentagainst a real DeepSeek Harness CLI (0.1.0-rc.6, repo-built launcher viacommandArgs):deer-workflow-dsh-e2e-ok);sandbox: "read-only"is honored (the harness runtime context reportsCurrent DSH file policy: read-only);{"answer":"workspace inspected under read-only policy","ok":true}) extracted from a prose-wrapped fenced-JSON final message.