All shelves / Mods / Workflow
cli-dispatch
By rbinar
cli-dispatch is a Claude Code workflow mod by rbinar.
Hands a task to DeepSeek, Gemini, Codex, OpenCode, or Copilot, and draws this session's workers above the prompt.
DrawsHolds a command
Install
The marketplace name is cli-dispatch.
/plugin marketplace add rbinar/cli-dispatch /plugin install cli-dispatch@cli-dispatch /reload-plugins /cli-dispatch:setup
It runs inside the Claude Code process. The side panel is only what the author's README names. Read the repo before you install, or run claude plugin validate on the plugin folder.
- Version
- 6.4.0
- License
- MIT
- Repo stars
- 10
- Last change
- 2026-10-13
What it can reach
- Draws in the session
- Holds a command
- Reaches the network or an outside service
- Sees tool calls
- Calls another program on this machine
Setup asks which backends you want and installs their wrappers. API keys go into a local browser form and never pass through Claude. On Claude Code 2.1.287 or later, a band above the prompt shows this session's live workers, and for 10 minutes after, each finished run's verify result. With no workers, nothing is drawn. Older Claude Code ignores the band. While a worktree run is live, an edit or write into that repo is refused, because an edit there would make the run's leak check blame the worker and skip verify. Bash writes are not caught. The runner isolates the job in a git worktree and runs your verify command. The worker CLIs talk to DeepSeek, Gemini, OpenAI, OpenRouter, or GitHub Copilot. Workers can write files and run commands. Real repo work stays in a worktree until you apply the patch. Codex has a read-only mode. The security page describes it. A status line fragment is optional, for a status line you already run. Session-start policy text is off unless setup turns it on. The preferred path starts the runner with no model turns of its own. On older Claude Code a Haiku forwarder starts it, on your own Claude login.
The plugin folder has no README. The install lines are the repository README. The band and the edit guard are in docs/features.md. The marketplace name is cli-dispatch. Worker CLIs are the network access. git is the local program. Source also checks whether a quiet worker process is still alive before the run is treated as finished. The optional status line fragment is not the band.
Demo

What it hooks into
session.startWhen a session startstool.callAround a tool call, where it can hold onemcp__cli-dispatch__dispatchui.renderDraws into the sessionAbovePrompt
Read from the on() calls in its hook modules. Open its source under Files to check what each one does.
Hooks 5
SessionStart · startupnode "${CLAUDE_PLUGIN_ROOT}/scripts/policy-inject.mjs"SessionStart · resumenode "${CLAUDE_PLUGIN_ROOT}/scripts/policy-inject.mjs"SessionStart · clearnode "${CLAUDE_PLUGIN_ROOT}/scripts/policy-inject.mjs"SessionStart · compactnode "${CLAUDE_PLUGIN_ROOT}/scripts/policy-inject.mjs"SessionStart · forknode "${CLAUDE_PLUGIN_ROOT}/scripts/policy-inject.mjs"
Files
The author's source, 3 files. They load when you open them.
Facts
- Author
- rbinar
- Category
- Workflow
- Marketplace
- cli-dispatch
- Folder
- plugins/cli-dispatch
- Version
- 6.4.0
- License
- MIT
- Repo stars
- 10
- Last change
- 2026-10-13
- Language
- JavaScript
- Files
- 132