wiki: publish pending edits (2026-10-20)
This commit is contained in:
@@ -3,8 +3,8 @@ title: Model Routing
|
||||
type: concept
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
verified_on: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
confidence: high
|
||||
tags: [routing, model, inference]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt, current-profile.md]
|
||||
@@ -20,6 +20,26 @@ How Hermes selects providers, applies combos, and enforces context limits.
|
||||
- Default model: `freellmapi-auto`
|
||||
- OmniRoute used for auxiliary roles: vision, skills_hub, approval, mcp, title_generation, web_extract, compression
|
||||
|
||||
> **Live `model:` block re-read 2026-10-20 — the default has moved.**
|
||||
> `model.default` is now **`meituan/longcat-2.5-preview:free`** (provider `nous`), not
|
||||
> `freellmapi-auto`. The block also carries `base_url`, `persist_switch_by_default` and `api_mode`.
|
||||
>
|
||||
> **The five `custom_providers` and their live base URLs:**
|
||||
>
|
||||
> | Name | Base URL | Host |
|
||||
> |---|---|---|
|
||||
> | `litellm` | `http://litellm:4000/v1` | LiteLLM proxy (m93p CT500) |
|
||||
> | `guacano` | `http://ollama:11000/v1` | Guanaco on CT205 |
|
||||
> | `Omniroute:20128` | `http://omniroute:20128/v1` | OmniRoute on m93p CT101 |
|
||||
> | `command-code` | `https://api.commandcode.ai/provider/v1` | remote |
|
||||
> | `omni-101` | `http://100.78.63.20:20128` | OmniRoute node `omniroute-1` (direct IP, not a DNS name) |
|
||||
>
|
||||
> Note the **two distinct OmniRoute endpoints**: `Omniroute:20128` (DNS, m93p CT101) and
|
||||
> `omni-101` (raw IP `100.78.63.20:20128`). `omni-101` is the pin on effectively every
|
||||
> model-calling cron job, and it has been the single point of failure in the 10-14, 10-16/17 and
|
||||
> 10-19 incidents — its `/api/health` reads `200 {"status":"ok"}` throughout, so **reachability
|
||||
> probes do not detect that failure class**; only job-level error text does.
|
||||
|
||||
## Context Enforcement
|
||||
- Three layers: model native → combo `data.config.context_length` → Hermes client cap
|
||||
- Effective context is the minimum of the three
|
||||
|
||||
Reference in New Issue
Block a user