Repository navigation
Add DeepSeek Harness as a coding agent - #14455
stjohn668-openclaw wants to merge 10 commits into
Conversation
|
|
Thanks for the research behind the version pin. A few things:
|
|
Thanks — pushed an update.
|
|
Both Greptile findings are fixed:
Each has a regression assertion in |
DSH boots a named profile, and the web profile its installer ships serves the harness's UI on a local port instead of running a terminal UI, so there is no permission flag to add and no prompt to seed: omarchy-agent boots `dsh web`. Every release DSH has published so far is a prerelease, and mise's npm backend lists only stable versions, so the package names 0.2.0-rc.2 outright. Drop the pin once a stable release exists. The menu mark is a new U+E90F glyph traced from simpleicons.org.
install/user/mise.sh only runs during provisioning, so the agent roster entry on its own left `dsh` failing as a command: on a fresh install, and on every install that predates it, until the user picked the agent, which installs it. Add the stub to user setup and to a migration. Name the version: every DSH release so far is a prerelease and mise's npm backend lists only stable versions.
`dsh web` serves the harness UI on a local port. Record that the port binds 127.0.0.1, so the manual answers whether the UI is reachable from the network.
The migration installed the stub for anyone missing it, which included a user who had removed Omarchy's preinstalls. Match the Muse migration and skip when ~/.local/state/omarchy/preinstalls-removed is present.
install/user/mise.sh now writes ~/.local/bin/dsh, so removing the preinstalls has to delete it too, the way it does for every other shipped agent wrapper.
6c4a244 to
2fdcd81
Compare
|
Rebased onto Heads up on the local test suite, both pre-existing on
|
`omarchy agent prompt` has no place to seed a task when the agent's UI is the harness's own web page, and the harness chooses its workspace there rather than from the directory it was launched in, so the `~/Work` start the other agents get does not decide what `dsh` can reach.
|
One more commit, covering two launch differences I hit while running
Both are noted in the same |
Preserve current agent and panel integrations while merging quattro. Provision wrappers unconditionally, respect existing commands and the preinstall opt-out in migrations, and remove only owned wrappers. Allocate distinct brand glyphs across the three independent integrations. Co-Authored-By: GPT-6 in Codex <noreply@openai.com> Co-Authored-By: Codex Medium (GPT-6.1-sol) <noreply@openai.com>
Co-Authored-By: GPT-6 in Codex <noreply@openai.com> Co-Authored-By: Codex Medium (GPT-6.1-sol) <noreply@openai.com>
Follow the existing Kimi and Crush one-shot pattern when a prompt is supplied; ordinary launches still open the browser UI. Bind task arguments after -- so option-like text stays literal instead of being treated as CLI flags. Co-Authored-By: GPT-6 in Codex <noreply@openai.com>
DSH consumes the first -- before passing its argument tail to the profile app. The headless app needs a second separator; otherwise an initial task such as --help opens profile help instead of running the task. Verified against the installed 0.2.0-rc.2 CLI with networking disabled. Co-Authored-By: GPT-6 in Codex <noreply@openai.com>
|
Thanks for bringing this up to date with quattro and fixing prompted launches, including the extra separator for the profile app. I've fast-forwarded my local checkout to Keeping |
DeepSeek Harness (dsh) joins the default agent picker, installed through mise as npm:@deepseek-ai/dsh pinned to 0.2.0-rc.2, since every release so far is a prerelease that mise's npm backend would skip. The launcher opens its browser UI with the danger-full-access permission preset, and runs a supplied prompt once through the headless profile, which is the only way dsh accepts one. The manual names its session-log and feedback uploads and how to turn them off. From #14455, superseding #9777. Co-authored-by: john st <njtoronto668@gmail.com> Co-authored-by: T2816 <zhangjf@tongtech.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DeepSeek Harness becomes a selectable default coding agent through
dsh,deepseek, ordeepseek-harness. Its official npm developer-preview release is pinned to0.2.0-rc.2, because mise’s normal npm version selection excludes prereleases.Omarchy opens the harness’s browser UI with DeepSeek’s no-approval permission preset. The web profile listens on loopback and uses the launch directory as its default workspace.
omarchy agent promptinstead runs the supplied task once through DeepSeek’s headless profile, keeping option-like prompt text literal.Provisioning and Refresh Applications recreate the lazy wrapper. The migration preserves existing commands and respects Remove Preinstalls; removal deletes only Omarchy’s recognized wrapper. The menu carries DeepSeek’s monochrome mark at U+E90F, distributed through an
omarchy-settingsrelease. It adds no region-specific configuration or usage collector.Related: #9777 proposes the same harness through a different integration.
No separate issue is closed.
Testing
Reran the following against
727f8e7in the Omarchy VM on 2026-10-14; all passed:bash test/shell.d/dsh-agent-test.shbash test/shell.d/mise-provision-test.shbash test/shell.d/default-agent-test.shbash test/shell.d/menu-test.sh./test/cliThese cover the aliases and pinned lazy installer, ordinary web launches, one-shot headless tasks with literal option-like prompts and the two separators, migration idempotence and the preinstall opt-out, preservation of user-managed launchers during migration/removal, removal of Omarchy's own wrapper, and menu ordering/font coverage. Shell syntax checks also passed for the launch, selection, provisioning, migration, and removal scripts.
The full
./test/allsuite and graphical acceptance suite were not rerun in this validation pass.