Skip to main content

Buyer guide

Junie Models and Credits: How to Keep Spend Predictable

Which model each task should run on, when BYOK, Junie Lite, or Junie Local beats credits, and the limits an administrator can set.

Reading time
3 min read
Sources
18 cited
In this piece
Junie+28 Positive

The bill follows the model each task runs on. Run routine Junie work on the Default model, move eligible work to your own keys or the free tiers, and set credit limits before spend grows. Every fact here is from JetBrains' documentation as of October 12, 2026.

When you need this

  • Credits run out mid-month because every task runs on the largest model.
  • Engineers want models JetBrains AI does not offer, or already pay for another provider.
  • Some code must stay on the developer's machine.
  • Finance asks why the bill shows calls to models nobody selected.

Evaluation criteria

  1. Start from the Default model

    Does each task run on a model sized for it?

    Look forStart routine work on Default, which JetBrains selects for price and quality and updates as models ship. Use Plan mode to plan on a stronger model and implement on a cheaper one. Increase reasoning effort only when a task needs it. JetBrains says higher effort costs more and takes longer without reliably better results.

  2. Know what each model costs

    Can engineers see what a task cost?

    Look forCheck session costs with /usage in Junie CLI. It reports tokens, models, cost, and the remaining balance. One credit buys US$1 of usage at provider API rates for input, cached, and output tokens per million. Check promotions too. In August 2026, JetBrains made Gemini 3.7 Flash the default at a temporary 40% discount.

  3. Use your own keys where they are cheaper

    Which teams already pay a model provider directly?

    Look forConnect OpenAI, Anthropic, Google, xAI, or OpenRouter keys in Junie CLI, or sign in through Copilot CLI with a GitHub Copilot subscription. A connected key takes precedence over JetBrains AI for the same model. Central Business admins can assign OpenAI, Google Vertex AI, Anthropic, or Amazon Bedrock by policy. Set a provider budget because these requests bypass Central credit limits.

  4. Move eligible work to the free tiers

    Which work could run on Junie Lite or a local model?

    Look forUse Junie Lite in JetBrains Air or Junie CLI with any JetBrains account. It runs Qwen 3.6 27B on JetBrains infrastructure. JetBrains calls it "virtually unlimited" for normal use and publishes no quota, because the model behind it can change. When that model reaches capacity, requests stop with no fallback, so keep deadline work on credits or your own keys. For local work, Junie Local runs Qwen3.6-27B at 4-bit on an Apple Silicon M5 Mac with 64 GB and macOS 26. Nothing leaves the machine. JetBrains reports results on par with Sonnet 4.5 on its private test set.

  5. Budget for helper models

    Does the budget include calls the engineer did not choose?

    Look forBudget for helper calls on your own keys too. Junie uses a second model from the same provider to summarize context and handle routing and memory. Anthropic tasks call Claude Haiku, and Google tasks call Gemini Flash. These calls appear on the provider bill even when the engineer did not select those models.

Questions to ask vendors

  1. Which models are enabled for our organization, and who reviews the list when the Default changes?
  2. Which teams should run on their own provider keys, and who owns those keys?
  3. Which repositories are approved for Junie Lite, which runs on JetBrains infrastructure?
  4. What per-user monthly limit applies to credits, and what limit applies to own-key spend at the provider?

Red flags

  • Maximum reasoning effort as a personal default.
  • Own-key spend with no budget at the provider, because Central credit limits do not cover it.
  • Workflows that depend on the model behind Junie Lite, which JetBrains may change without notice.
  • A local-model plan that assumes hardware below an M5 Mac with 64 GB of memory.

Products in this piece

Sources

Official documentation
13
Public source
5
  1. Junie docs: Model selectionOfficial documentationjunie.jetbrains.com
  2. Junie docs: Plugin model settingsOfficial documentationjunie.jetbrains.com
  3. Junie docs: Junie CLI quickstartOfficial documentationjunie.jetbrains.com
  4. Junie docs: Bring Your Own KeyOfficial documentationjunie.jetbrains.com
  5. Junie docs: GitHub Copilot as a providerOfficial documentationjunie.jetbrains.com
  6. Junie docs: Junie LiteOfficial documentationjunie.jetbrains.com
  7. Junie docs: Junie LocalOfficial documentationjunie.jetbrains.com
  8. JetBrains Junie blog: Junie Local launch (Aug 24, 2026)Official documentationblog.jetbrains.com
  9. Junie docs: Custom LLMsOfficial documentationjunie.jetbrains.com
  10. JetBrains Central Console docs: Plans and pricingOfficial documentationjetbrains.com
  11. JetBrains Central Console docs: AI providersOfficial documentationjetbrains.com
  12. JetBrains Central Console docs: AI credit limitsOfficial documentationjetbrains.com
  13. JetBrains Junie blog: Junie's new default runs on Gemini 3.7 Flash (Aug 17, 2026)Official documentationblog.jetbrains.com
  14. AdComplex1867 on Reddit r/Jetbrains: Junie is now costing me about US$5 a day (Sep 30, 2025)Public sourcereddit.com
  15. dzhiurgis on Hacker News: Gemini through Junie (Apr 22, 2026)Public sourcenews.ycombinator.com
  16. soco on Hacker News: Junie crashes and daily spend (Feb 4, 2026)Public sourcenews.ycombinator.com
  17. lowercased on Hacker News: Junie as a daily driver on the US$30 plan (Sep 24, 2026)Public sourcenews.ycombinator.com
  18. FpUser on Hacker News: Junie on Gemini Flash for professional work (Jul 4, 2026)Public sourcenews.ycombinator.com