Twitter/X

Defaulting engineers to open-weight models (GLM 5.2 and Kimi 2.7) via an LLM…

2026-06-28 · 15:24 UTC ·@ccatalini ·1 min read

Brief

Brian Armstrong outlines operational tactics to keep AI spend flat while token usage grows: default engineers to open-weight models (GLM 5.2, Kimi 2.7), preprocess and route prompts to the right model, and implement cache-aware requests (LibreChat hit rate 5%→60%). These changes reportedly cut AI spend nearly in half without suppressing usage.

Why it matters

Defaulting engineers to open-weight models (GLM 5.2 and Kimi 2.7) via an LLM gateway lowered cost pressure—91% of employees never hit usage caps, so the team moved to cheaper defaults instead of lowering caps or adding friction.

Key details

  • Better routing and caching cut costs: LibreChat's cache hit rate rose from 5% to 60% after changes, and preprocessing prompts to route planning to frontier models and execution to cheaper models helped cut AI spend nearly in half while token usage keeps growing.
  • Operational rules to reduce wasted tokens include starting fresh sessions when switching tasks, scoping file context narrowly, disconnecting unused tools, making requests cache-aware, and automating model selection rather than having humans pick models.
Source evidence

Markets route around bottlenecks

Brian Armstrong (@brian_armstrong)

How to keep AI spend flat while token usage grows exponentially: Not with friction and spend alerts. With better defaults, routing, and caching.

Better Defaults (not Usage Caps) – Engineers can choose any model they want, but defaults matter. We’re experimenting with defaulting to open weight models like GLM 5.2 and Kimi 2.7 through our LLM gateway, while still encouraging engineers to choose the right model for the task. 91% of our employees were never hitting their usage caps, so instead of lowering caps and driving up alerts, we're moving to cheaper defaults. Note that code reviews use a diversity of models, so they can check each other's work.

Better Routing – In our custom harnesses, we preprocess prompts and route to the best model for the job, considering cache hits and model pricing. For instance, you may want a frontier model for planning, but not for execution where they can be overkill. Ultimately, humans shouldn't be choosing models - AI can automate this task.

Better Caching – Cache misses are the easiest way to drive your cost up. All of our requests are cache aware, so we’re reusing a warm cache wherever possible. For example, our cache hit rate went from 5% → 60% in LibreChat once properly implemented.

Keep Context Lean – Start fresh sessions when switching tasks. Scope file context narrowly. Disconnect unused tools. Don't just compact. The goal isn't fewer tokens used, it's fewer tokens wasted.

Better Visibility – Our engineers can use as many tokens as they want, from whatever model they want, but we’ve made usage visible – and the more you spend on AI, the more impact we expect.

The goal isn't to suppress usage. It's to build the infrastructure that makes exponential growth sustainable.

Putting this into practice has cut our AI spend nearly in half, while our token usage continues to grow.

— https://nitter.net/brian_armstrong/status/2070670644577280109#m