multi-cli-runtime

Route multi:* subagents to the correct CLI runtimes via a unified helper.

88|7|Updated Apr 5, 2026

Search Tags:#automation #routing #runtime #subagent #cli-dispatch #multi-cli-runtime

Ready to run

npx skills add https://github.com/greenpolo/cc-multi-cli-plugin --skill multi-cli-runtime

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: multi-cli-runtime
Source: https://github.com/greenpolo/cc-multi-cli-plugin/tree/main/plugins/multi/skills/multi-cli-runtime
Command: npx skills add https://github.com/greenpolo/cc-multi-cli-plugin --skill multi-cli-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables consistent routing of multi:* subagents to the appropriate CLI runtimes by delegating calls to a shared companion runtime, simplifying orchestration for Claude Code tasks.

Core Features & Use Cases

Centralized, rules-driven dispatch of multi:* subagents to codex/gemini/cursor/copilot/qwen runtimes.
Lightweight helper that standardizes how tasks are forwarded to the chosen CLI.
Use Case: When a multi:* subagent needs to execute a writer, debugger, or researcher task via the correct CLI without manual CLI handoffs.

Quick Start

Invoke the primary helper to forward a task to the selected CLI with a single standardized call.

Frequently Asked Questions about multi-cli-runtime

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I route subagent tasks to multiple CLI runtimes like cursor or gemini?▼

You route subagent tasks by invoking a shared companion helper that forwards each task to the correct CLI runtime with a single standardized Bash call, preserving stdout and forwarding flags for roles like writer, debugger, and researcher.

What is a multi-cli runtime dispatcher for subagents?▼

A multi-cli runtime dispatcher is a centralized, rules-driven helper that routes multi:* subagents to the correct CLI runtimes—such as codex, gemini, cursor, copilot, or qwen—simplifying orchestration without manual CLI handoffs.

Do I need a Node.js environment to use multi-cli runtime routing?▼

Yes, multi-cli runtime routing requires a node-based companion helper to standardize task dispatch across CLI runtimes, enforcing a single Bash call per execution while forwarding role framing.

Can I forward role-specific tasks like researcher or explorer to different CLI tools?▼

Yes, role-specific tasks such as researcher, explorer, planner, or debugger are forwarded to the selected CLI runtime through the helper, which preserves role framing and forwards flags during the single Bash dispatch.

Why use a unified helper instead of calling CLI runtimes directly for subagent dispatch?▼

A unified helper standardizes how tasks are forwarded to each CLI, enforcing a single Bash call per dispatch and preserving stdout, which eliminates inconsistent manual handoffs across runtimes.

What limitations exist when routing subagents to CLI runtimes through a shared helper?▼

The helper enforces a single Bash call per dispatch and requires the node-based companion, limiting execution to one standardized call per subagent routing event without parallel multi-call bursts.