Back to plugins
dsh-agent-conductor Cover

dsh-agent-conductor

Dispatch tasks in-session to 11 external agent CLIs (Codex/Claude Code/TraeCode/OpenCode/Gemini/Cursor/Kimi/Qwen/Copilot/WorkBuddy/Grok) and stream results back

github.com/akqwpeter-prog/dsh-agent-conductor
13 MIT Author akqwpeter-prog Updated

Install

dsh plugin --profile web add github:akqwpeter-prog/dsh-agent-conductor

dsh-agent-conductor

Keep each agent CLI installed, and let your DSH session decide who gets the task — dispatching out and bringing the result back.

What problem it solves

Codex, Claude Code, Cursor and friends each have their strong suits, but getting them to take turns inside a DSH session usually means manual copy-paste: hand the task to an external CLI, wait for it to finish, then paste the output back. This “conductor” plugin (inspired by Multica’s agent-squad idea) lets your in-session agent recognize delegation requests and dispatch tasks headlessly to 11 external agent CLIs (Codex, Claude Code, TraeCode, OpenCode, Gemini, Cursor, Kimi, Qwen, Copilot, WorkBuddy, Grok), with stdout streamed straight back as the basis for the answer.

The implementation is deliberately small: one SKILL.md plus a 90-line, zero-dependency dispatch.py (Python standard library only) — a read-only script the host never notices. It can also be installed as a host-only bundle providing the conductor_dispatch tool, sharing the same CLI registry with no client half and no impact on the Web UI.

Key features

  • 11 headless CLIs: Codex, Claude Code, TraeCode, OpenCode, Gemini, Cursor, Kimi, Qwen, Copilot, WorkBuddy, Grok — command shapes centralized in the dispatch.py registry
  • Description-triggered: the SKILL.md description match lets the model recognize delegation intent on its own, no manual tool call
  • Results become the answer: stdout flows back into the session as the basis for the reply
  • Zero-dependency engine: dispatch.py uses only the Python standard library; install is copying one folder
  • Optional host-only bundle: the conductor_dispatch tool shares the CLI registry, with no client side
  • Verified vs. pending list: Codex is tested on a real machine; Claude Code / TraeCode / OpenCode follow official docs; the rest are marked pending

Quick start

Install (pick one):

# Skill: copy into any skills root
mkdir -p .dsh/skills/conductor
cp -R skills/conductor/. .dsh/skills/conductor/

# Bundle: host-only tool
dsh plugin --profile web add github:akqwpeter-prog/dsh-agent-conductor

No restart needed — just describe the need in your next message and it triggers automatically:

Dispatch Codex to translate this doc into Traditional Chinese

Have Claude Code look up the cause of this error

Prereq: install the CLI of whichever agent you want to dispatch (e.g. npm i -g @anthropic-ai/claude-code). Codex needs to run inside a trusted git repo — set CONDUCTOR_CWD=/path/to/git/repo in ~/.dsh/secrets/media-tools.env, and add sandbox_mode = "workspace-write" to ~/.codex/config.toml to let a dispatched agent write files. Note: dispatch consumes the target CLI’s login quota.

Who it is for

  • Users with several agent CLIs installed who want to orchestrate them from one DSH session
  • Power users who don’t want to write a plugin and would rather have DSH lead an “agent squad”
  • Anyone who wants the in-session agent to own sub-tasks like translating, troubleshooting, or implementing a piece in isolation
Tags Agent Automation

Compiled from the project README · All rights belong to the original author

Report issue / Request removal

Related plugins