Repository navigation
v2.7.0 — Features & Provider Updates
Sprint: ClawRouter-inspired features — toolCalling flag, multilingual intent detection, benchmark-driven fallback, request deduplication, pluggable RouterStrategy, Grok-4 Fast + GLM-5 + MiniMax M2.5 + Kimi K2.5 pricing.
✨ New Models & Pricing
- feat(pricing): xAI Grok-4 Fast —
$0.20/$0.50 per 1M tokens, 1143ms p50 latency, tool calling supported - feat(pricing): xAI Grok-4 (standard) —
$0.20/$1.50 per 1M tokens, reasoning flagship - feat(pricing): GLM-5 via Z.AI —
$0.5/1M, 128K output context - feat(pricing): MiniMax M2.5 —
$0.30/1M input, reasoning + agentic tasks - feat(pricing): DeepSeek V3.2 — updated pricing
$0.27/$1.10 per 1M - feat(pricing): Kimi K2.5 via Moonshot API — direct Moonshot API access
- feat(providers): Z.AI provider added (
zaialias) — GLM-5 family with 128K output
🧠 Routing Intelligence
- feat(registry):
toolCallingflag per model in provider registry — combos can now prefer/require tool-calling capable models - feat(scoring): Multilingual intent detection for AutoCombo scoring — PT/ZH/ES/AR script/language patterns influence model selection per request context
- feat(fallback): Benchmark-driven fallback chains — real latency data (p50 from
comboMetrics) used to re-order fallback priority dynamically - feat(dedup): Request deduplication via content-hash — 5-second idempotency window prevents duplicate provider calls from retrying clients
- feat(router): Pluggable
RouterStrategyinterface inautoCombo/routerStrategy.ts— custom routing logic can be injected without modifying core
🔧 MCP Server Improvements
- feat(mcp): 2 new advanced tool schemas:
omniroute_get_provider_metrics(p50/p95/p99 per provider) andomniroute_explain_route(routing decision explanation) - feat(mcp): MCP tool auth scopes updated —
metrics:readscope added for provider metrics tools - feat(mcp):
omniroute_best_combo_for_tasknow acceptslanguageHintparameter for multilingual routing
📊 Observability
- feat(metrics):
comboMetrics.tsextended with real-time latency percentile tracking per provider/account - feat(health): Health API (
/api/monitoring/health) now returns per-providerp50LatencyanderrorRatefields - feat(usage): Usage history migration for per-model latency tracking
🗄️ DB Migrations
- feat(migrations): New column
latency_p50incombo_metricstable — zero-breaking, safe for existing users
🐛 Bug Fixes / Closures
-
fix(mitm): Compile MITM utilities as NodeNext ESM during prepublish, copy the CommonJS MITM server into the standalone artifact, and resolve MITM data paths without relying on Next.js aliases in packaged runtime.
-
fix(build): Move the local
.tmp/wine32Wine prefix out of the isolated Next.js build path so Windows Electron packaging artifacts cannot triggerEACCESscans during Node 24 builds. -
fix(build): Copy the
wreq-jsnative runtime directory into the isolated Next.js standalone output so packaged Playwright/E2E starts can load the instrumentation hook on Linux. -
fix(api): Validate the Codex Responses websocket bridge and
/v1/batchesJSON payloads with Zod before use, keepingrequest.json()route validation green and returning explicit 400 responses for invalid bodies. -
fix(providers): Add explicit typing to provider alias and category helpers so the strict
typecheck:noimplicit:coreCI gate passes. -
fix(ui): Keep the upstream proxy provider detail page labeled with a fallback "Managed via Upstream Proxy Settings" management surface when translations are unavailable.
-
fix(electron): Harden the production desktop CSP by removing
unsafe-evaloutside development and adding object, base URI, form action, frame ancestor, and worker restrictions. -
fix(cli): Replace shell-interpolated setup and privileged command execution paths with argument-based
spawn/execFilehelpers for database setup, Tailscale sudo commands, MITM DNS edits, and certificate install/uninstall flows. -
fix(ui): Keep provider icons resilient by using direct
@lobehub/iconscomponents first, then local PNG/SVG fallbacks, avoiding the@lobehub/uipeer runtime in the dashboard. -
close(#411): better-sqlite3 hashed module resolution on Windows — fixed in v2.6.10 (f02c5b5)
-
close(#409): GitHub Copilot chat completions fail with Claude models when files attached — fixed in v2.6.9 (838f1d6)