Routes work between Orca, SendMessage, ecp, and the embedded browser.
npx skills add https://github.com/coseto6125/claude-setup --skill agent-routing-coseto6125
Please help me install this Agent Skill. Skill: agent-routing Source: https://github.com/coseto6125/claude-setup/tree/main/skills/agent-routing Command: npx skills add https://github.com/coseto6125/claude-setup --skill agent-routing-coseto6125
ecp peers plan before fanning work out so each dispatched task owns a disjoint surface of the code graph, and chains overlapping targets with task-create --deps. - Browser routing: Any task that needs to see a page — rendering a URL, screenshotting a dev server, checking layout — goes to Orca's embedded browser via orca-cli, never a hand-written Playwright script; desktop windows go to computer-use. - Guide drift detection: The bundled check-anchors.sh script verifies that three quoted passages from the Orca orchestration guide still match the installed Orca version, warning when the overrides in SKILL.md go stale. - Use Case: Before dispatching three workers to refactor separate modules, run ecp peers plan --targets to confirm their blast radii do not intersect, then brief each Claude worker with SendMessage while a codex worker gets its task through an Orca terminal. ## Quick Start Ask the agent to decide which runner and channel should handle a task, for example whether to dispatch a code change through Orca or message an existing Claude session directly.High-intent search queries and answers about installing and using this skill.
Route by message type: lifecycle messages like worker_done, heartbeat, and escalation stay on Orca, while content between Claude Code sessions — questions, findings, diff reviews — goes over SendMessage. SendMessage carries plain text only, so a lifecycle message sent that way updates no task.
Run `ecp peers plan --targets <symbols> --direction both --format json` before dispatching. Its clusters group targets whose blast radii intersect, so you give each cluster its own task and chain overlapping targets with `task-create --deps` instead of dispatching them together.
No. Drive Orca's embedded browser through `orca-cli` for anything that renders a page, including URLs, dev servers, and web apps. The playwright MCP entry was removed because the embedded browser covers the work, and desktop windows that are not pages go to `computer-use` instead.
No. ListAgents reports Claude Code sessions only, so every channel to codex, opencode, gemini, or a bare shell runs through Orca terminals. Export ECP_SESSION_ID when creating the codex terminal so ecp can track its session.
The listing reports only sessions holding a dirty surface that acted in the repo recently. Clean worktrees, sessions quiet past the liveness window, and agents editing by absolute path from another cwd are absent, so treat Orca task specs as the roster and ecp status as supporting evidence.
FlexNetOSIdentifies direct and transitive dependencies of a symbol to assess refactoring impact.
cbrostromCoordinate supervised Orca workers with task DAGs, threaded messages, and decision gates.
AradotsoDiscover and message Claude Code instances via a local MCP broker.
Patasse97Orchestrate the full AgentHub lifecycle in a single command.