google-gemini/gemini-cli

More configurable numeric routing

Open

#21805 opened on Mar 10, 2026

View on GitHub
 (6 comments) (0 reactions) (1 assignee)TypeScript (103,992 stars) (13,657 forks)batch import
aiq/routingarea/agenthelp wantedkind/enhancementkind/featurepriority/p2status/bot-triaged

Description

What would you like to be added?

I would like to have much more control over routing. For numerical routing, this would mean controlling what levels get sent to which models, for example something like:

  • <10 -> local gemma
  • <30 -> 2.5 flash
  • <80 -> 3 flash
  • >80 -> 3 pro

Why is this needed?

Currently, the only routing available is to choose between the flash and pro models for the current major version. This is quite restrictive, especially as even 3 flash is quite capable (and quite quota- and rate-limited).

Additional context

No response

Contributor guide

Tech stack
typescriptnodejs
Domain
cliai
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScript knowledgeUnderstanding of AI model routingFamiliarity with Gemini CLI codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Examine the existing routing configuration and model selection logic in the codebase, likely in files such as 'router.ts' or 'config.ts'. Review comments and maintainer responses in this issue for implementation hints. Identify how thresholds are currently hardcoded and propose a flexible configuration approach.