HiRoute

Use smart task routing

Model routing decides “which model should handle this stage.” Task routing decides “which execution agent should own this work.” You can enable either capability independently or combine them.

The sections below begin with the Desktop configuration path. Linux headless can publish the same plan through routing preview/apply, connect an Agent through agents connect preview/apply, and then use the same Worker commands. Obtain exact fields from the installed schema.

What to delegate

Delegation works best for independently executable work with a clear goal, working directory, and deliverable—for example, implementing a bounded feature, investigating a group of test failures, or producing a research summary. The main agent discovers allowed plans, selects a fitting scenario, and retrieves the result.

Do not delegate coordination, plan discovery, status checks, waits, or result summaries. An execution agent cannot recursively create another delegation layer.

Enable delegation on a plan

  1. Open Smart routing and create or edit a plan.
  2. Under Task delegation, turn on Allow delegation to an execution agent.
  3. Choose one execution agent for the plan: Codex CLI or Claude Code. A plan has one executor and no automatic executor fallback.
  4. Check the required execution environment when prompted, then publish the plan.

A missing installation does not block saving the plan, but the chosen execution agent must pass its dependency check before a task can start. Give the plan a specific name and purpose that describe fitting tasks and expected results, so a main agent can choose it correctly.

Allow a main agent to use the plan

Open Agents, choose the Codex or Claude Code installation that will act as the main agent, then open Task delegation skill:

  1. Enable the task delegation skill.
  2. Select the published plans it may discover and invoke.
  3. Save and complete the skill check.

You can now explicitly ask for delegation in the agent's normal conversation. If you choose the default-delegation behavior, the main agent may also select a plan for suitable independent work. Desktop lists accepted work on the Tasks page.

Use the same production path from Terminal

After installing the HiRoute CLI, discover executors and plans:

hiroute worker executors
hiroute worker plans

Then start a task:

hiroute worker exec \
  --plan <PLAN_ID> \
  --cwd /absolute/path/to/project \
  --title "Fix the parser regression" \
  -- "Find the failure, implement the smallest fix, and run the relevant tests"

Keep the returned submission key, task ID, and run ID. They recover uncertain submissions and identify the task for status, continuation, or cancellation.

Permission and cancellation boundaries

The default approve-all lets the selected harness use its native read, write, command, and network behavior. It is not an operating-system sandbox. If you need a restriction, select only a policy that the page or CLI says the harness supports. An unsupported restriction fails before the prompt instead of silently widening access.

Cancellation stops the selected run; it does not undo files or external effects already produced. Concurrent tasks are not serialized merely because their working directories overlap. The caller decides whether overlapping execution is appropriate.