From 41ffc87ed70f08955b2f80d6959908aa816716c1 Mon Sep 17 00:00:00 2001 From: Tin Chi Lo Date: Fri, 21 Aug 2026 19:56:23 -0700 Subject: [PATCH] docs(complexity-router): state the reasoning boundary as inclusive The mapping's last comparison is a strict 'score < complex_reasoning', so a score landing exactly on the boundary falls through to REASONING. The table said greater than. --- litellm/router_strategy/complexity_router/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/litellm/router_strategy/complexity_router/README.md b/litellm/router_strategy/complexity_router/README.md index 943479cb357..67237f0a898 100644 --- a/litellm/router_strategy/complexity_router/README.md +++ b/litellm/router_strategy/complexity_router/README.md @@ -32,7 +32,7 @@ The weighted sum is mapped to tiers using configurable boundaries: | SIMPLE | < 0.10 | - | Basic questions, greetings | | MEDIUM | 0.10 - 0.25 | `simple_medium` | Standard queries | | COMPLEX | 0.25 - 0.50 | `medium_complex` | Technical, multi-part requests | -| REASONING | > 0.50 | `complex_reasoning` | Chain-of-thought, analysis | +| REASONING | >= 0.50 | `complex_reasoning` | Chain-of-thought, analysis | The three boundaries must ascend, and any key you leave out is filled from the shipped default, so setting one boundary without the others can put them out of order. A set that decreases would strand the tier between the inverted pair and silently route its traffic to a costlier one, so it is rejected at config load with a message naming the resolved values. Set every boundary you need to move, not just one.