Skip to content

v1.4.6

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Jun 09:07
v1.4.6
196de7c

AgentGate 1.4.6 — Scenario routing by model name / 按模型名做场景路由

What's new

  • Route by client model name. A route's provider can now match on the requested model name, so background subtasks (e.g. Claude Code's haiku calls) go to a cheaper provider while the main conversation stays on your primary one. Works across Claude Code / Codex / Gemini.
  • Config write verification. After applying a client config (Codex / Claude Code / Gemini / others), AgentGate reads the file back and verifies it landed correctly — a mis-written config now reports an error instead of a false success.
  • Slimmer Routes page. Removed the duplicated "Conditions" summary block, and the fallback chain now only shows in failover mode, so the page is much shorter.

本次更新

  • 按客户端模型名路由。 路由里的供应商现在可按请求的模型名匹配，把后台子任务(如 Claude Code 的 haiku 调用)分流到便宜供应商，主对话仍走主力供应商。Claude Code / Codex / Gemini 三端通用。
  • 配置写后校验。 应用客户端配置(Codex / Claude Code / Gemini 等)后，AgentGate 会读回文件确认写入正确，写歪时报错而不是假成功。
  • 路由页更精简。 去掉重复的「条件」汇总区块，失败转移链路仅在故障转移模式显示，页面短一大截。

Why it matters / 为什么重要

Scenario routing is the most-requested way to cut cost — cheap models for cheap work, strong models where it counts. 场景路由是最被需要的省钱方式——便宜活儿用便宜模型，关键处用强模型。

Full changelog / 完整更新

See CHANGELOG.md for the full itemized list.

Assets 19
Loading