zevairouter 1.0.259 → 1.0.260

package/cli/app/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Unreleased
 
+# v1.0.260 (2026-08-19)
+
+## Features
+- **`/v1/models` now advertises capabilities and token limits.** The response was just `{id, object, owned_by}`, so any client that auto-discovers models had nothing to work with — OMP's `openai-models-list` discovery fell back to conservative defaults (small context window, tools assumed off) and then aborted large tool-using requests against models that handle them fine: `kr/claude-opus-5` chats normally when called directly, but OMP dropped the connection at 96 ms with `IN 0 / OUT 0`. Each LLM entry now carries pattern-matched `capabilities` plus `context_length` and `max_completion_tokens` under the snake_case names the OpenAI convention uses (a client matching `context_length` previously found nothing, guessed from the model name, guessed high, and so never compacted before hard-failing upstream). Verified live: 164/228 models expose metadata, up from 0; the rest are non-LLM kinds with no context window.
+
 # v1.0.259 (2026-08-19)
 
 ## Features

package/cli/app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zevairouter",
-  "version": "1.0.259",
+  "version": "1.0.260",
   "description": "Self-hosted AI router: many providers, one OpenAI-compatible /v1 endpoint and dashboard",
   "bin": {
     "zevai": "cli/cli.js"

package/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zevairouter-cli",
-  "version": "1.0.259",
+  "version": "1.0.260",
   "private": true,
   "description": "ZevaiRouter CLI - Start and manage ZevaiRouter server",
   "bin": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zevairouter",
-  "version": "1.0.259",
+  "version": "1.0.260",
   "description": "Self-hosted AI router: many providers, one OpenAI-compatible /v1 endpoint and dashboard",
   "bin": {
     "zevai": "cli/cli.js"