---
title: "Junie Eco Mode"
description: "Junie Eco Mode splits coding tasks into two phases: planning with the user’s selected model and implementation with a cheaper model, cutting costs significantly. In two internal benchmarks, average model cost per task dropped 57.3% (benchmark B) and 48.1% (benchmark A), while average resolve rates changed by less than one percentage point. The architect only reads code and produces a structured plan in about 15 steps, never making changes. The builder then follows the plan exactly, editing files, running builds and tests, and fixing issues. Eco mode is enabled by default for many configurations in JetBrains Air EAP and Junie CLI."
---

# Junie Eco Mode

[Jetbrains](https://yomu.fyi/company/jetbrains) · Helena Klause · Oct 28, 2026

**Type:** Announcement

## Summary

Junie Eco Mode splits coding tasks into two phases: planning with the user’s selected model and implementation with a cheaper model, cutting costs significantly. In two internal benchmarks, average model cost per task dropped 57.3% (benchmark B) and 48.1% (benchmark A), while average resolve rates changed by less than one percentage point. The architect only reads code and produces a structured plan in about 15 steps, never making changes. The builder then follows the plan exactly, editing files, running builds and tests, and fixing issues. Eco mode is enabled by default for many configurations in JetBrains Air EAP and Junie CLI.

## Context

AI coding agents typically run a single expensive model for every step of a task, including repetitive execution steps like ‘run the tests again’, leading to unnecessary costs.

## Takeaways

- Eco mode reduced average model cost per task by 48% to 57% on internal benchmarks across 50 model-and-effort configurations, while average resolve rate changed by less than one percentage point.
- The architect model produces a structured plan (Goal, Scope, Where, Approach, Tests, Risks) in about 15 steps without writing code; the builder model then implements the plan exactly.
- Eco mode is enabled by default in JetBrains Air EAP and Junie CLI for many configurations, but can be disabled; it only activates for code-change tasks and is unavailable for certain model/effort combos.

## FAQ

### Why not guess task difficulty upfront to choose a model?

Junie avoids upfront guessing because task difficulty is unpredictable from the request. Eco mode has the smart model always look first, ensuring every task gets planning from the expensive model, then the cheap model executes a written plan.

### When does Eco mode not step in?

Eco mode only activates for tasks that require code changes you intend to keep. For questions, explanations, project setup, or read-only commands, the chosen model handles the entire task. It is also unavailable in /remote sessions and with some model-and-effort combinations.

### How does the handoff between models work?

The architect model creates a structured plan with fixed fields (Goal, Scope, Where, Approach, Tests, Risks). The builder model receives the entire conversation plus the plan and executes without switching back to the expensive model. Each task has a single handoff.

**Tags:** [Agentic Development](https://yomu.fyi/topic/agentic-development), [Cost Optimization](https://yomu.fyi/topic/cost-optimization), [IntelliJ IDEA](https://yomu.fyi/topic/intellij-idea), [JetBrains](https://yomu.fyi/topic/jetbrains)

- Source: [Jetbrains](https://blog.jetbrains.com/junie/2026/10/junie-eco-mode)
- Source URL: https://blog.jetbrains.com/junie/2026/10/junie-eco-mode
- Ingested by Yomu: 2026-10-28T15:00:15.242Z

[Read original post](https://blog.jetbrains.com/junie/2026/10/junie-eco-mode)
