dsh-cli-bridge

╭───────────────────────────────────────────────────────╮
│                                                       │
│               dsh ⇄ claude code · codex               │
│                                                       │
│    Run Claude Code & Codex inside DeepSeek Harness    │
│               — watch every step, live                │
│                                                       │
│            live · autonomous · zero setup             │
│                                                       │
╰───────────────────────────────────────────────────────╯

What it does

One request in the chat. Claude Code or Codex doing real work — on screen, in
real time, under your control.

dsh-cli-bridge hands work to Claude Code and Codex, then keeps you and
DeepSeek Harness in the loop for the whole job:

[!IMPORTANT]
Why this exists — the built-in Claude Code and Codex integration runs in
the background and returns only the final message. You can't see what it is
doing, and it bills you twice. dsh-cli-bridge shows the whole job on screen,
keeps the details out of your conversation, and gives DeepSeek the controls.

The difference

And the rest

The headline is watching it live. The rest is what makes it safe to let Claude
Code or Codex loose on a project:

• 👥 Multi-account, isolated — each account is kept separate; one login
  never touches another.
• 🌐 Any provider — Claude Code can reach DeepSeek, OpenRouter, or any
  compatible provider.
• 🌿 Its own copy & automatic merge — several tasks each get their own copy;
  finished work is merged back automatically, one at a time, and conflicts are
  kept for you.
• 🧭 It asks clearly — when it needs a decision, it asks you plainly instead
  of guessing.
• 🔒 Respects your settings — it follows your Read Only / Workspace Write /
  Full Access choice, and adds no rules of its own.
• ⚙️ Model & effort per task — each task can name its own model and how hard
  to try, or use sensible defaults.

Install

dsh plugin --profile web add dsh-cli-bridge

Usage

Getting started

1. Install the plugin once, in a terminal:

   dsh plugin --profile web add dsh-cli-bridge

2. Open DeepSeek Harness and start a conversation.

3. Ask, in the message box, what you want. For example:

   "Use Claude Code to add a login page."

   DeepSeek takes it from there: it walks you through signing in (a box opens in
   the browser for the code) and runs the work with Claude Code or Codex while
   you watch.

Signing in (accounts)

The first time you ask for something, DeepSeek helps you sign in to Claude Code
or Codex. A box opens in the browser — type the code and press Enter.

Each account stays separate, so you can keep more than one. Just ask:

• "Add my other Claude Code account."
• "Make that one the default."
• "Use my Claude Code API key instead of a login."

What you can ask for

• One task — "Use Claude Code to fix the failing tests."
• Several tasks at once — "Use Codex to add the login page, and Claude Code
  to write the tests." Each runs on its own copy of the project and is merged
  back when done.
• A specific model or effort — name a model loosely ("use opus", "use
  sonnet") or ask it to think harder. /cli models lists exactly what each
  delegate accepts, and anything close is understood.

Manual or automatic

By default, nothing happens without you: if Claude Code or Codex has a question,
it asks you, right in the chat.

To let it work more on its own, type /cli auto decide on (it answers its own
questions), /cli auto continue on (it keeps going through remaining work), and
/cli auto review on (it checks the finished work). Use off instead of on
to undo any of them.

/cli tells you when the switches can actually act. Auto decisions are made by
the same DeepSeek model that is running the conversation, so a switch needs a
model route — when there is none, every question still comes to you, and it says
so instead of quietly doing nothing. A task that ran under auto reports which
switches were on and which model decided.

Watching and steering

Everything runs live in the conversation — every command, every file change.
While it runs you can answer its questions, tell it what to do next, or stop it.

Where the work goes

One task runs right in your project. Several at once each run on their own copy
(a git branch) and are merged back when done. If two changes touch the same
line, nothing is lost — you are told there is a conflict to resolve.

Doing it yourself (optional)

You never need to. But typing /cli shows what's ready and your accounts, and
/cli models, /cli login claude personal and /cli auto let you drive it by
hand if you prefer.

Support

dsh-cli-bridge is free to use and funded by the people it saves money. If
it keeps the Claude Code / Codex bill off your own, sponsor it.

• Use it freely — personally or commercially, with your own modifications.
• Sponsor to redistribute — publishing, forking, or offering it as a service
  is the one paid gate (a sponsorship or a commercial licence).
• Contribute — the project stays source-available while its author can still
  license it commercially. See LICENSE and
  CONTRIBUTING.

Licence

Source-available — © 2026 hviana. Free to use, funded by sponsors,
redistribution gated. The inlined open-source components keep their own
licences; see THIRD-PARTY-NOTICES.md.