dsh-agent-team-gui

What it solves

• A single model/route cannot cover planner, implementer, and reviewer roles effectively.
• One-off multi-agent dispatch lacks persistence, reusability, observability, and recovery.
• Multi-model collaboration lacks a unified view of Token usage, DAG state, retries, and quality gates.

Who it’s for

• Developers and teams building reusable multi-model workflow teams in DSH.
• Advanced users who want per-role model, tool policy, Token limits, and fallback routes.
• Ops/platform users who need to observe long-running DAGs, retries, quality gates, and official Token usage.