Skip to content

adr: add DeepSeek Harness as an inner engine #554

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vesc-baek wants to merge 1 commit into
base: main
Choose a base branch
from
Open

adr: add DeepSeek Harness as an inner engine #554

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions adrs/deepseek-harness.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# DeepSeek Harness as a harness

Ask: add DeepSeek Harness (`dsh`) as another inner engine, same seat as pi / opencode / codex / claude.

Not the DeepSeek model provider (that's PR 265). The harness itself: https://github.com/deepseek-ai/deepseek-harness

Why we'd want it: it's the loop DeepSeek measures their agent benches in, and it already speaks JSON-RPC (and ACP). Transport-wise that looks like the Codex adapter, not a new protocol.

The work, as we read it from the existing four:

- a `dsh` adapter through `defineHarness` / `runTurn`
- rebind its tools onto QM's sandbox (same brain/hands split as the others)
- add `dsh` to `HARNESS_IDS`, or do issue 542 first so this doesn't touch the closed set

We're not sending an implementation. If this is in scope we'd use it. If you'd rather keep the set at four, that's fine.

Status: request, no code.