Proposal: experimental host for DeepSeek Harness (dsh)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- node.js, python, typescript
- Domain
- developer-experience, tooling
Research direction
Start with plugin/opencode/tokeneconomizer.ts and the recent adapter PRs mentioned in the issue, then read docs/PLUGIN.md for host conventions. Check whether dsh 0.2.x supports tool-free single turns and persistent per-tool settings before settling the side-call and pruning behavior. Done means an experimental host adapter with offline tests, documented verified behavior and tested versions, plus live-session evidence that learned context reaches the model.
Written by the indexing model from the issue text.
Description
Would you take a PR adding DeepSeek Harness (dsh, npm @deepseek-ai/dsh) as an experimental host?
There are no dsh entries in this repo yet, but several community ports exist as separate repos, and each one reimplements the engine in TypeScript. I'd rather add dsh to this repo and keep this repo's Python engine.
Plan:
- A thin TypeScript plugin, modelled on
plugin/opencode/tokeneconomizer.ts, that forwards dsh's session, prompt and tool events tote-hookand returns injected context. No second engine. - First cut: micro-skills and the loop guard. Side calls would run through
dsh headless "<prompt>"with a--patchoverlay that strips tools. If dsh cannot run a tool-free single turn, side calls stay off by default, as on Droid and agy. - Tool pruning only once I've confirmed dsh has a persistent per-tool setting; until then "nothing yet", like opencode.
- Offline tests, a verified-behaviour section in
docs/PLUGIN.md, a supported-versions row (dsh 0.2.x is still pre-release, so I'd list the exact versions tested), and evidence from a live session that a learned fact reached the model.
Before I start, is this in scope? And are there conventions for new hosts that I should follow beyond what the recent adapter PRs show?
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 500
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 124
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/TokenEconomizer
-
Pi: paused model calls are reported as "not signed in" when the model's provider comes from an extensionPossibly taken @balcsida claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/TokenEconomizer#288 ·
Maintainers usually reply within 1 day
-
TokenEconomizer: repository-planted code runs in the plugin process; tmp writes follow symlinksPossibly taken @kevinveenbirkenbach claimed this 2 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
microsoft/TokenEconomizer#260 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
microsoft/TokenEconomizer#232 ·
Maintainers usually reply within 1 day
-
CommandCode supportOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/TokenEconomizer#205 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/TokenEconomizer#193 ·
Maintainers usually reply within 1 day
All issues in microsoft/TokenEconomizer
Similar issues
-
[Bug]: reme CLI crashes when the running server used a relative config pathPossibly taken @nurlanmnn claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/ReMe#770 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
sickn33/agentic-awesome-skills#2437 ·
Maintainers usually reply within 1 day
-
site-bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ethereum/consensus-specs#5846 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 74/100
BrainLesion/BraTS#200 ·