Skip to content

Make Codex and Claude Code subscriptions go further: a local model router that gives routine agent work to economical models and keeps your strongest model for the hard parts.

docs: lead the README with the subscription use case (#177)

澄潭6d2c45c38c34
diff --git a/README.md b/README.md
index 9f1aad93..ca878abf 100644
--- a/README.md
+++ b/README.md
@@ -7,8 +7,8 @@
</p>
<p align="center">
- <strong>Route agents by task. Route models by stage.</strong><br>
- A local-first routing and coordination engine for long-horizon agent tasks.
+ <strong>Make Codex and Claude Code subscriptions go further.</strong><br>
+ A local model router that gives routine agent work to economical models and keeps your strongest model for the hard parts.
</p>
<p align="center">
@@ -31,14 +31,17 @@
</a>
</p>
-HiRoute is a local control and execution layer for long-horizon agents. It brings model
-sources, reusable routing plans, agent connections, bounded failover, and execution evidence
-into one system, available through a Desktop application or a headless CLI and daemon.
-
-Decision-based routes choose again on each new user turn. Tool continuations in the same turn
-keep the frozen decision, helping the model reuse its growing context prefix. A context rebuild
-can require a new decision when HiRoute can no longer recognize the continuation or reuse its
-previous decision. Choosing again can also keep the same model; cache reuse depends on the provider.
+Keep using Codex, Claude Code, Qoder, Pi or DeepSeek Harness. With a smart-saving plan, HiRoute
+judges each new message: routine work such as reading code or gathering facts can go to an
+economical model, while design decisions and difficult fixes stay with your subscription or
+primary model. Subscriptions, API keys and local models are managed in one place, and each
+session shows which model actually ran, its usage and its cost. Independent tasks can also be
+delegated to other agents.
+
+Tool calls within a turn usually keep that turn's decision, so the growing context prefix stays
+cacheable. HiRoute decides again on a new user message, or when a context rebuild breaks the
+previous continuation, and may keep the same model; cache reuse depends on the provider. HiRoute
+runs locally as a Desktop application or a headless CLI and daemon.
## News
diff --git a/README.zh-CN.md b/README.zh-CN.md
index 9962098a..8eed7241 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -7,8 +7,8 @@
</p>
<p align="center">
- <strong>按任务选择 Agent,按阶段选择模型。</strong><br>
- 面向长程 Agent 工作、本地优先的智能路由与协作引擎。
+ <strong>让 Codex 和 Claude Code 的订阅更耐用。</strong><br>
+ 在本地运行的模型路由:常规工作交给经济模型,难题留给最强的模型。
</p>
<p align="center">
@@ -31,12 +31,14 @@
</a>
</p>
-HiRoute 是长程 Agent 的本地控制与执行层。它把模型来源、可复用路由计划、Agent 接入、有边界的
-故障接力和执行证据放在同一套系统里,同时提供 Desktop 应用以及无界面 CLI 和后台服务。
+继续使用你熟悉的 Codex、Claude Code、Qoder、Pi 或 DeepSeek Harness。使用智能省钱计划时,
+HiRoute 会在每条新消息到来时判断接下来的工作:读代码、查资料这类常规工作可以交给经济模型,
+设计取舍和疑难修复留给订阅或主力模型。订阅、API Key 和本地模型集中管理,每个会话实际用了哪个
+模型、用量和成本都可以查看;独立任务还可以委派给其他 Agent。
-使用决策的路由会在每个新用户轮次重新判断,同轮工具续接保持冻结决策,让模型持续复用增长中的
-上下文前缀。上下文重建后,如果 HiRoute 无法识别原来的续接关系或复用此前决策,才需要再次判断。
-重新判断也可以继续原模型;缓存实际能否复用取决于供应商。
+同一轮里的工具调用通常沿用本轮决策,让增长中的上下文前缀持续复用缓存;新用户消息到来,或上下文
+重建打断原有续接时,HiRoute 才重新判断,也可能继续原模型。缓存实际能否复用取决于供应商。HiRoute
+在本地运行,提供 Desktop 应用以及无界面 CLI 和后台服务。
## News · 最新动态