◀The Ambient Key Ambush
LOGIC JetBrains/thinkrail #1168 · ★ 8.2kfix(host): prefer configured connections for new chatsA real, public pull request, signed as made with Claude Code. See it on GitHub ↗
IN THE WORLD

Stops new AI chats from silently billing pay-per-use API keys instead of your ThinkRail subscription.

REACH

Made by JetBrains as an open-source incubator project, ThinkRail has 8,245 GitHub stars and is used by developers running parallel AI coding agents.

WHAT IT MEANS

When starting a new chat without a saved default model, ThinkRail now prefers your configured subscription over stray shell environment API keys, preventing surprise pay-per-use charges.

  • JetBrainsmakes it
RED · how I did it
  • If you picked a specific model, then use your picked model.
  • If no connections exist, then no model is available.
  • If your saved default is an available ambient key, then use the saved ambient key.
  • GONE Otherwise, if an ambient key is available, then it can win over your subscription.
GREEN · how I do it now
  • If you picked a specific model, then use your picked model.
  • If no connections exist, then no model is available.
  • If your saved default is an available ambient key, then use the saved ambient key.
  • NEW Otherwise, prefer your configured subscription first, and only use an ambient key if none exists.

WHERE ThinkRail's new chat screen, right when you start a fresh conversation without picking a model.

SCENE You open a new chat in ThinkRail without choosing a model. You have a paid subscription configured, but your terminal also has a pay-per-use API key sitting in the background.

Your model choice
Whether you picked a model for this chat or saved one as your default. (No pick or saved default · Saved ambient key · Picked a specific model)
Available connections
Which AI provider connections are currently active on your machine. (Subscription and ambient key · Ambient key only · Subscription only · No connections)