mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-04 02:31:27 +00:00
629b464cd6
Agent harnesses send a lot of operational turns that relay or reformat tool output rather than reason about it, and the cheapest built-in tier was SIMPLE. NON_REASONING adds a rung below it, behind enable_non_reasoning_tier so an already-deployed router cannot move. The toggle is what keeps it safe. The tier set feeds the classifier rubric, the response-format enum, the escalation ladder and the savings baseline, so a default-on fifth tier would have changed what every existing router sends and where its traffic lands. Off, the ladder, rubric, wire labels and baseline are byte-identical to before. On, the rung is added at index 0, escalation walks up out of it, and it can never win the savings baseline. It requires an llm or custom classifier and a model of its own: the v1 score ladder has no rung below simple_medium and the v2 artifact is trained on four classes, so the heuristic scorers cannot produce the tier and a router that enabled it there would pay for a bullet nothing reaches. The dashboard follows the same flag, and the edit modal now reads the tier back from the stored config rather than assuming four keys, since it rewrites tiers wholesale on save and would otherwise delete a hand-written tier on any edit. |
||
|---|---|---|
| .. | ||
| litellm-dashboard | ||
| Dockerfile | ||
| nginx.conf | ||