DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to route drafting and review to separate model groups with Hi Route

Use custom task branches so drafting and review each get the model that fits their category and difficulty.

Who it is forA team lead or developer who wants cheap models for first drafts and a stronger model for review, without one model handling both.

The problemA single routing rule cannot tell drafting work from review work, so review either gets an underpowered model or drafting wastes premium usage.

The outcomeHi Route picks a task category first, then the simple or complex degree within it, so drafting and review use different model groups.

What you need first

  • macOS 15 or later on Apple silicon or Intel, or Linux x86_64 or ARM64 (aarch64) for the headless CLI and daemon
  • An existing Codex or Claude Code subscription, a registered API, or a compatible custom API to connect
  • A decision model connection (Bailian, OpenRouter Jev, TypeSafe, or a compatible endpoint) for model-based judgment
  • An Agent client such as Codex or Claude Code configured to use HiRoute

Steps

  1. Run hiroute service start --output json after installing Hi Route, then run hiroute system status --output json to confirm the service is up.
  2. Connect the decision model you want to use for judgment under Models, then Decision models.
  3. Create a routing plan with custom task branches for drafting and review, giving each category a regular group and, where needed, a primary group.
  4. Publish the routing plan and connect your Agent client or expose it as a Worker plan.
  5. Review the sessions view to confirm each turn shows its category and the model group that actually ran.

Prompt for your agent

Using the HiRoute repo at https://github.com/higress-group/HiRoute, configure a routing plan with separate drafting and review custom task branches for <target project>. Report which model group each branch uses and the category HiRoute chose for two sample turns. Verify that a low drafting score does not change the review category.

Caveat. The README describes custom branches but does not list the exact category names or model group limits, so check the routing plan editor before publishing.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page