dsh-crew

Usage

• Directly in conversation, say "dispatch X to ds-flash" or "dispatch X to ds-pro", and subagent executes the task
• Dispatch count and real-time progress shown in Claude Code task UI
• HUD status line segment: ⚙dsh 1▶pro 2m14s 21.7k/606 ✓3 (current tier / elapsed time / token usage / completion count)
  • For local development, statusline/statusline.sh or statusline/worker-segment.sh can be independently integrated
• Long-running tasks: CC has timeout limits on MCP calls (MCP_TOOL_TIMEOUT adjustable), long tasks can have orchestrator use dsh_spawn_worker + dsh_worker_result(wait_seconds) polling
• Local development and debugging: claude --plugin-dir /path/to/dsh-crew to temporarily load

Usage

• In interactive TUI, select "spawn ds-pro to ..." to dispatch tasks; Active/Done panels show progress
• codex exec mode can also directly call dsh_run_worker

Usage

• Pick ds-flash or ds-pro as the agent to dispatch tasks
• dsh_worker_config reads or overrides the session defaults

Usage

• Pick ds-flash or ds-pro as the agent to dispatch tasks

Configuration

In DSH settings page → DSH Crew → Multimodal (or directly edit ~/.config/dsh-crew/config.json):

Vision provider (image viewing):

• native / deepseek-native (DeepSeek's own VL model — tried first automatically for every built-in provider whenever a key is available)
• `claude-cod