hviana/dsh-cli-bridge
Bridges DSH to Claude Code and Codex so their work runs live inside the harness: every command, file change and reasoning step visible.
Closes the visibility gap that makes delegating to a coding CLI unpleasant. The built-in shape of that delegation is: run the CLI in the background, get a spinner, receive a final paste. Here every command, every file changed and every line of thought appears in DSH as it happens, so DeepSeek can steer, answer and review the work step by step rather than reading a summary after the fact — and it hands you the question when it should not decide. Isolation is handled rather than assumed: each task gets its own copy of the project, finished work is merged back automatically one at a time, and conflicts are kept for you instead of being resolved silently. Multi-account isolation means parallel logins do not leak into each other, and because the executing CLI can point at any compatible provider, the account and the model are separate choices. The result is a plugin that makes a second agent loop auditable from inside the session you are already watching.
Install
dsh plugin --profile web add dsh-cli-bridgeThe README's Install block, which is the whole installation section — one line in a terminal, then open DeepSeek Harness and start a conversation. Usage needs no further setup: you ask in the message box (the README's example is "Use Claude Code to add a login page") and DSH walks you through signing in, opening a browser box for the code, then runs the work while you watch. Typing /cli shows what is ready and which accounts are connected; the README says you never need to, but it is the status surface when a login or a provider is not behaving.
Compatibility
Works with Claude Code or Codex as the executing CLI, and Claude Code itself can be pointed at DeepSeek, OpenRouter or any compatible provider rather than Anthropic only. It honours the harness permission presets — Read Only, Workspace Write or Full Access — and the README states it adds no rules of its own, so the guardrails you set in DSH are the guardrails that apply. Accounts are kept separate: one login never touches another, which is the reason the README frames it as many accounts side by side rather than one shared credential. Each task can name its own model and effort level, or fall back to sensible defaults, and it asks plainly when it needs a decision instead of guessing.
Details
- Repo: hviana/dsh-cli-bridge
- Category: Agent Capabilities
- Stars: 1
- Version: 0.1.7 (npm)
Alternatives
YYTbit/dsh-plugin-pi-bridge · egnmosk/dsh-browser-bridge · vibeinging/dsh-agent-budget