← Coding

JunieJunie

JetBrains

编程Coding IDEIDE 多模型Multiple models 本地Local partial lifecycle: active 核验Checked 2026-10-23

Junie 是 JetBrains 官方的 AI coding agent。 它的形态是插件加 CLI：插件装进 JetBrains IDE，CLI 跑在终端与 CI/CD 里。

三个招牌：先出计划再写代码、用真调试器排障、不锁模型。 Plan mode 产出结构化计划文档，确认后才实现。排障时它接管调试会话、下断点，而不是加 println。模型上支持 BYOK，也能接本地模型。

Junie is JetBrains' coding agent, installed as a plugin — the official install page states "The Junie plugin is not bundled and not enabled in JetBrains IDEs by default" — and extended in March 2026 by a standalone Junie CLI for the terminal, any IDE, CI/CD and GitHub / GitLab. Its official framing is LLM-agnostic: "Junie supports all the top-performing models from OpenAI, Anthropic, Google, and Grok." On the IDE side it plans before it codes and, since GA, drives your IDE's real debugger rather than adding println.

适合与不适合When to use it, when not to

适合三类人。一是在用 JetBrains IDE、希望在同一环境里用 agent 的人。二是看重「先出计划再写代码」与多模型 / BYOK 的团队。三是需要在终端或 CI/CD 里复用同一个 agent 的人（Junie CLI）。

不适合中国大陆用户——官方许可页写明 Junie：

官方原文："not available to users in Mainland China due to regional restrictions"

也不适合 AI Enterprise 档用户（官方写明该档暂不含 Junie）。 也不适合需要厂商托管云后台的人（本形态没有「关机续跑」的官方说法）。

People already using JetBrains IDEs (IntelliJ IDEA / PyCharm / WebStorm / GoLand and more) who want an agent in the same environment. Teams that value "plan before code" and multi-model / BYOK flexibility. Anyone who needs the same agent in the terminal or CI/CD (Junie CLI).

Not a fit for users in Mainland China — the official licensing page states "Junie coding agent is not available to users in Mainland China due to regional restrictions"; nor for AI Enterprise tier users (that page states the tier does not currently include Junie), nor for anyone who needs a vendor-hosted cloud background environment.

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-20

出品属地Origin: 国外出品foreign-made　国外主体（网信办公示名单未见对应备案主体）。foreign entity (no matching filing entity in the CAC registry).
国内使用Direct access: 直连未核验direct unknown　junie.jetbrains.com 对 curl 直连与代理都返回 403（反爬拦截），本方法无法判定可达性。junie.jetbrains.com returns 403 to curl both direct and proxied (anti-bot) — reachability cannot be judged by this method.
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-20 检索 13 批附件，https://www.cac.gov.cn/2024-04/02/c_1713729983803145.htm）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (13 batch attachments searched 2026-10-20, https://www.cac.gov.cn/2024-04/02/c_1713729983803145.htm); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

8 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 结论：不锁模型，能自带 API Key，也能接本地模型。

官方把自己定位成 LLM-agnostic。 Junie CLI 的发布博客把这句话写得很直白：

官方原文："Junie supports all the top-performing models from OpenAI, Anthropic, Google, and Grok"

官方把 BYOK（自带 API Key）算进了定价模型里。官网与定价页另列两条路：

本地模型 —— via OpenAI-compatible APIs，含 Ollama 与 LM Studio
第三方云模型 —— OpenAI / Anthropic / Google / xAI

IDE 侧的默认模型换过。 帮助页 Models（2025-10-14 修订）写 Default 是 OpenAI 的 GPT-5。 2026-08-17 官方博客又称默认改成了 Gemini 3.7 Flash。

本地推理的说法前后变过。 帮助页当时写「暂不能在离线模式用本地模型」。 2026-08 的 Junie Local 又支持在本机跑 Qwen3.6-27B。

具体的模型清单与各档可得性，官方未在一页内给全。 （已查 help Models 页与 AI 定价页。）
Conclusion: no model lock-in; you can bring your own API key, and local models work too.

The official pages position it as LLM-agnostic. The Junie CLI launch blog states it bluntly:

Official wording: "Junie supports all the top-performing models from OpenAI, Anthropic, Google, and Grok"

Official pricing builds BYOK (bring your own API key) into the model. The site and pricing page list two more routes:

Local models — via OpenAI-compatible APIs, including Ollama and LM Studio
Third-party cloud models — OpenAI / Anthropic / Google / xAI

The IDE-side default model has changed. The help page Models (revised 2025-10-14) says Default is OpenAI's GPT-5. The 2026-08-17 official blog then says the default became Gemini 3.7 Flash.

The local-inference story also changed over time. The help page then said "local models cannot be used in offline mode yet". Junie Local from 2026-08 supports running Qwen3.6-27B on your own machine.

The concrete model list and per-tier availability are not given in full on any single official page. (help Models page and the AI pricing page checked.)
运行位置Where it runs: 它是插件，不是独立编辑器；另有独立的 Junie CLI。

官方 Install 页的原话：

官方原文："The Junie plugin is not bundled and not enabled in JetBrains IDEs by default"

宿主覆盖 JetBrains 全家桶与 Android Studio：

CLion、GoLand、IntelliJ IDEA、PhpStorm、PyCharm Pro
Rider、RubyMine、RustRover、WebStorm 与 Android Studio

官方还给了各 IDE 的最低版本。例如 IDEA Ultimate / PyCharm Pro / WebStorm / GoLand 需 2024.3.2+。

第二条腿是 Junie CLI（2026-03 进入 Beta）。终端、任意 IDE、CI/CD 与 GitHub / GitLab 都能跑。 ReSharper 2026.2 把它带进 Visual Studio（Preview）。 2026-08 起另有本机推理的 Junie Local。
It is a plugin, not a standalone editor; there is also a standalone Junie CLI.

The official Install page states:

Official wording: "The Junie plugin is not bundled and not enabled in JetBrains IDEs by default"

Hosts cover the whole JetBrains family plus Android Studio:

CLion, GoLand, IntelliJ IDEA, PhpStorm, PyCharm Pro
Rider, RubyMine, RustRover, WebStorm and Android Studio

The official pages also give per-IDE minimum versions. E.g. IDEA Ultimate / PyCharm Pro / WebStorm / GoLand need 2024.3.2+.

The second leg is Junie CLI (entered Beta in 2026-03). It runs in terminals, any IDE, CI/CD and GitHub / GitLab. ReSharper 2026.2 brings it into Visual Studio (Preview). Since 2026-08 there is also Junie Local with on-device inference.
本地文件Local files: 它只动你当前项目的文件；出项目要单独批准。

每轮执行后，Junie 会列出本次新增与修改的文件。每个文件都有 diff 查看链接。在 Done 面板里，你能逐文件选择性回滚。然后再决定接受还是拒绝整次执行。它执行的命令输出，可以在 Junie 的终端里看。

「项目外」是一条显式边界。 Action Allowlist 里有两条独立规则，默认都需要批准：

「Read outside project」
「Write outside project」

想限定它处理哪些文件与目录，用 .aiignore。它的语法和 gitignore 同款。官方提醒：它只保护内容，文件名与目录名仍然可见。

IDE 语义索引的实现细节，官方未单列。 （已查 aiignore 与 diffs-and-review 两页。）
It only touches files in your current project; leaving the project needs separate approval.

After each run, Junie lists the files added and modified. Every file has a diff-view link. In the Done panel you can selectively roll back file by file. Then you decide to accept or reject the whole run. Output of the commands it runs can be seen in Junie's terminal.

"Outside the project" is an explicit boundary. The Action Allowlist has two separate rules, both requiring approval by default:

"Read outside project"
"Write outside project"

To limit which files and directories it handles, use .aiignore. Its syntax is the same as gitignore. The official pages warn: it protects content only; file names and directory names remain visible.

Implementation details of the IDE semantic index are not broken out officially. (the aiignore and diffs-and-review pages checked.)
关机后的任务Tasks after shutdown: 没有厂商托管的后台：任务跑在你打开的那个环境里。

IDE 形态依赖 IDE 进程常驻。本形态下，官方没有描述「厂商托管、关机续跑」的后台环境。它在 Code mode 下能自主跑多步任务、测试与构建。但这些动作都在你打开的 IDE 与本机上进行。

Junie CLI 把运行面扩展到终端、CI/CD 与 GitHub / GitLab。 那里是「你自己的运行环境」，不是厂商沙箱。

官方博客另称 Junie 能：

官方原文："run long tasks while you focus on other things"

但官方未给出后台并发或时长额度。

厂商托管的后台执行环境，官方未说明。 （已查 modes、licensing 与 CLI 发布博客三处。）
There is no vendor-hosted background: tasks run inside the environment you have open.

The IDE form depends on the IDE process staying open. In this form the official pages describe no vendor-hosted "keeps running after shutdown" background. In Code mode it can autonomously run multi-step tasks, tests and builds — but all of that happens in your open IDE and on your machine.

Junie CLI extends the runtime surface to terminals, CI/CD and GitHub / GitLab. Those are "your own execution environments", not a vendor sandbox.

The official blog also says Junie can:

Official wording: "run long tasks while you focus on other things"

But no background concurrency or duration quota is given officially.

A vendor-hosted background execution environment: not stated officially. (the modes, licensing and CLI launch blog checked.)
工具与扩展Tools & extensions: 能力按模式分层，招牌是用真调试器。

四种模式：

Code mode —— 拆出多步计划并自主执行：跑命令、建文件、改代码、跑测试
Ask mode —— 只读探索与分析
Plan mode —— 先产出可编辑的结构化计划，再实现
Auto —— 由它自选

调试不是加日志，是真的接管调试会话。 GA 版起，Junie 能启动或接管调试会话。它在项目码、库码乃至反编译的 .class 文件里下断点。它还能查看栈帧与线程状态，并求值表达式。

官方原话："uses the debugger, not println"

另有 PR 审查与 git 工作流。还有 /demo：跑一遍功能，产出视频 / 截图 / HTML 报告。

MCP 官方支持，但目前只有 stdio 传输。 mcp.json 分两级：全局 ~/.junie/mcp.json，项目 .junie/mcp。它能自动推荐相关的 server。

官方原文："Only MCP servers that use the Standard Input/Output (stdio) transport type are currently supported"
Capabilities are layered by mode; the signature move is using the real debugger.

Four modes:

Code mode — breaks work into a multi-step plan and executes autonomously: runs commands, creates files, edits code, runs tests
Ask mode — read-only exploration and analysis
Plan mode — first produces an editable structured plan, then implements
Auto — it picks

Debugging is not adding logs — it genuinely takes over the debug session. Since the GA release, Junie can start or take over debug sessions. It sets breakpoints in project code, library code and even decompiled .class files. It can inspect stack frames and thread state, and evaluate expressions.

Official wording: "uses the debugger, not println"

There is also PR review and git workflows. And /demo: runs through a feature and produces video / screenshots / an HTML report.

MCP is officially supported, but currently only the stdio transport. mcp.json comes in two levels: global ~/.junie/mcp.json, project .junie/mcp. It can auto-recommend relevant servers.

Official wording: "Only MCP servers that use the Standard Input/Output (stdio) transport type are currently supported"
上下文与记忆Context & memory: 计划是可提交的工件，Guidelines 是持久上下文。

Plan mode 的计划不是一次性对话。计划文档存在 .junie/plans，可以提交进版本库。它按产品需求、技术设计、交付阶段（可选测试策略）分页。需求含糊时，Junie 会先反问，确认之后才实现。

.junie/guidelines.md 是持久层。它会被加进每一个任务，可以版本控制、可以复用。官方另有一个 junie-guidelines 目录。

官方还称 Junie 能 context-aware by default，并说它做得到 next-task prediction。连上 JetBrains IDE 后，还有语义重构与智能搜索。

上下文窗口与压缩策略，官方未给数字。 （已查 customize-guidelines 与 out-of-beta 博客两处。）
Plans are committable artifacts; Guidelines are persistent context.

Plan mode's plan is not a throwaway conversation. Plan documents live in .junie/plans and can be committed to version control. They are paginated by product requirements, technical design, delivery phases (optionally a test strategy). When requirements are vague, Junie asks back first and only implements after confirmation.

.junie/guidelines.md is the persistent layer. It is added to every task, can be version-controlled and reused. The official pages also mention a junie-guidelines directory.

The official pages also call Junie context-aware by default and say it does next-task prediction. Connected to a JetBrains IDE, it adds semantic refactoring and smart search.

Context window and compaction strategy — no numbers given officially. (customize-guidelines and the out-of-beta blog checked.)
权限与限制Permissions & limits: 默认每个动作都要审批。 Brave Mode 能一次放开，但官方不建议。

官方把动作分成 safe 与 sensitive 两类。

官方原文："Most terminal commands, code execution, and execution of MCP tools are considered to be sensitive actions, and Junie by default requires explicit approval from the user"

Brave Mode 可以一次性放开所有敏感动作。

官方原话："using brave mode is not recommended"

Action Allowlist 按类型加白：

Terminal（支持正则）、RunTest、Build、Preview
MCP、Read outside project、Write outside project
Edit build scripts —— 它可能触发代码执行，所以单独设闸

ls / cd / pwd 默认免确认。

.aiignore 保护文件内容。但官方提示：Brave Mode，或命中白名单的命令，可以绕过。
By default every action needs approval. Brave Mode opens everything at once, but the official pages do not recommend it.

The official pages split actions into safe and sensitive.

Official wording: "Most terminal commands, code execution, and execution of MCP tools are considered to be sensitive actions, and Junie by default requires explicit approval from the user"

Brave Mode can release all sensitive actions in one switch.

Official wording: "using brave mode is not recommended"

The Action Allowlist whitelists by type:

Terminal (regex supported), RunTest, Build, Preview
MCP, Read outside project, Write outside project
Edit build scripts — it can trigger code execution, so it gets its own gate

ls / cd / pwd need no confirmation by default.

.aiignore protects file content. But the official pages note: Brave Mode, or commands matching the allowlist, can bypass it.
适合什么任务Best for: 适合三类人，不适合另外三类。

适合：

已经在用 JetBrains IDE（IntelliJ IDEA / PyCharm / WebStorm / GoLand 等）的人
看重「先出计划再写代码」与多模型 / BYOK 的团队
需要在终端或 CI/CD 里复用同一个 agent 的人（Junie CLI）

不适合：

中国大陆用户
AI Enterprise 档用户（官方写明该档暂不含 Junie）
需要厂商托管云后台的人

中国大陆这条是官方许可页的硬规定：

官方原文："Junie coding agent is not available to users in Mainland China due to regional restrictions"

本形态也没有「关机续跑」的官方说法。
Fits three kinds of people, does not fit three others.

Fits:

People already on JetBrains IDEs (IntelliJ IDEA / PyCharm / WebStorm / GoLand etc.)
Teams that value "plan first, code second" plus multi-model / BYOK
People who need the same agent reused in terminals or CI/CD (Junie CLI)

Does not fit:

Users in mainland China
AI Enterprise tier users (the official pages state that tier does not include Junie for now)
People who need a vendor-hosted cloud background

The mainland-China point is a hard rule on the official licensing page:

Official wording: "Junie coding agent is not available to users in Mainland China due to regional restrictions"

This form also has no official "keeps running after shutdown" story.

头号误解Top misconception

以为 Junie 是独立 IDE，它其实是 JetBrains IDE 的插件（另有 CLI 形态）Assuming Junie is a standalone IDE — it is a plugin inside JetBrains IDEs (plus a separate CLI form)
以为 Junie 可用在 AI Enterprise 档，官方明确写该档暂不含 JunieAssuming Junie is available under the AI Enterprise tier — the official page states that tier does not currently include Junie
以为 MCP 支持远程服务器，官方写明目前只支持 stdio 传输Assuming MCP remote servers work — the docs state only the stdio transport is currently supported

未知项清单Known unknowns

美元口径的订阅价（官方页本次以人民币年付呈现，本站不折算）
上下文窗口大小与压缩策略的具体参数（官方未给数字）
Junie Local 支持的机型与模型范围
各 JetBrains AI 档位对 Junie 的可用性勾选细节（官方未说明，只取到许可页对 Enterprise 档的排除）

Subscription price in USD (the official page presented CNY annual pricing in the 2026-10-08 check; this site does not convert)
Concrete parameters of context-window size and compaction strategy (no numbers given officially)
Machine models and model range supported by Junie Local
Per-JetBrains-AI-tier availability details for Junie (not stated officially; the 2026-10-08 check only captured the licensing page's exclusion of the Enterprise tier)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-23，内容更新日content updated on 2026-10-08。

类型Type	名称Name	链接Link
docs	JetBrains · Junie 官方产品页（「smart coding agent」定位与支持的 IDE 列表）JetBrains · Junie official product page ("smart coding agent" positioning and supported IDE list)	https://www.jetbrains.com/junie/
docs	JetBrains · Junie 帮助文档（Modes / Guidelines / Action Allowlist / .aiignore / MCP / Models）JetBrains · Junie help docs (Modes / Guidelines / Action Allowlist / .aiignore / MCP / Models)	https://www.jetbrains.com/help/junie/get-started-with-junie.html
pricing	JetBrains · AI in IDEs 定价页（AI Free / Pro / Ultimate 与 credits 配额，2026-10-08 核）JetBrains · AI in IDEs pricing page (AI Free / Pro / Ultimate with credits quotas, verified 2026-10-08)	https://www.jetbrains.com/ai-ides/buy/
docs	JetBrains · 许可与订阅（配额周期、地区限制、AI Enterprise 档不含 Junie）JetBrains · Licensing and subscriptions (quota cycles, regional restrictions, AI Enterprise tier excludes Junie)	https://www.jetbrains.com/help/junie/licensing-and-subscriptions.html
docs	JetBrains · MCP 文档（仅 stdio，全局与项目级 mcp.json）JetBrains · MCP docs (stdio only; global and project-level mcp.json)	https://www.jetbrains.com/help/junie/model-context-protocol-mcp.html
docs	JetBrains · Action Allowlist 与 Brave Mode（敏感动作审批）JetBrains · Action Allowlist and Brave Mode (approval for sensitive actions)	https://www.jetbrains.com/help/junie/user-approval.html
changelog	JetBrains · 官方博客：Junie 离开 Beta（2026-06-17，Plan mode / 真调试器）JetBrains · Official blog: Junie out of beta (2026-06-17, Plan mode / real debugger)	https://blog.jetbrains.com/junie/2026/06/junie-coding-agent-out-of-beta/
changelog	JetBrains · 官方博客：Junie CLI 进入 Beta（2026-03-09，LLM-agnostic / BYOK）JetBrains · Official blog: Junie CLI enters beta (2026-03-09, LLM-agnostic / BYOK)	https://blog.jetbrains.com/junie/2026/03/junie-cli-the-llm-agnostic-coding-agent-is-now-in-beta/
changelog	JetBrains · Junie 官方博客列表（变更源）JetBrains · Junie official blog index (change source)	https://blog.jetbrains.com/junie/

实测记录Measured runs

本档未跑端到端编码任务；能力结论来自官方文档，编码向测量协议见 protocols/coding/_protocol.md。

实测建议：重点测两件事。

一是 Plan mode 的计划文档能否作为可提交工件复用。二是 agentic debugging 在真实失败用例上，能否快过「加日志」。

This site has not completed measured runs. The test protocol is at protocols/coding/_protocol.md.

Suggested measurement: focus on two things.

First, whether Plan mode's plan documents can be reused as committable artifacts. Second, whether agentic debugging beats "add logging" on real failing cases.

形态：插件 + CLI 两条腿Form factor: two legs — plugin + CLI

先说结论：它是插件，不是独立编辑器。

官方 Install 页的原话是：

The Junie plugin is not bundled and not enabled in JetBrains IDEs by default.

宿主覆盖 JetBrains 全家桶与 Android Studio：

CLion、GoLand、IntelliJ IDEA、PhpStorm
PyCharm Pro、Rider、RubyMine、RustRover、WebStorm

2026-03 起多了 Junie CLI 这条腿。 官方博客称 Junie 由此从「IDE 原生 AI」走向「ecosystem-level AI」。终端、任意 IDE、CI/CD 与 GitHub / GitLab 都能用。 ReSharper 2026.2 又把 Junie 带进 Visual Studio（Preview）。

Conclusion first: it is a plugin, not a standalone editor.

The official Install page states:

The Junie plugin is not bundled and not enabled in JetBrains IDEs by default.

Hosts cover the whole JetBrains family plus Android Studio:

CLion, GoLand, IntelliJ IDEA, PhpStorm
PyCharm Pro, Rider, RubyMine, RustRover, WebStorm

Since 2026-03 there is the additional Junie CLI leg. The official blog says this moves Junie from "IDE-native AI" to "ecosystem-level AI". It works in terminals, any IDE, CI/CD and GitHub / GitLab. ReSharper 2026.2 further brings Junie into Visual Studio (Preview).

关键设计：Plan mode 与真调试器Key designs: Plan mode and the real debugger

Plan mode 把「计划」做成一等工件（GA 版新增）。产出是结构化文档，含产品需求、技术设计、交付阶段（可选测试策略）。文档存在 .junie/plans，可以提交。需求含糊时它先反问，确认后才实现。官方给的用法建议很具体：计划用强模型，实现用便宜模型。

Agentic debugging：官方原话是 Junie「opens the debugger」，而不是加 println。它能启动 / 接管调试会话，在项目码、库码乃至反编译的 .class 文件里下断点。还能查看栈帧、线程状态，并求值表达式。

Plan mode makes the "plan" a first-class artifact (new in the GA release). The output is a structured document covering product requirements, technical design, delivery phases (optionally a test strategy). Documents live in .junie/plans and can be committed. When requirements are vague it asks back first and implements only after confirmation. The official usage advice is concrete: use a strong model for the plan, a cheap model for implementation.

Agentic debugging: the official wording is that Junie "opens the debugger" rather than adding println. It can start / take over debug sessions and set breakpoints in project code, library code and even decompiled .class files. It can also inspect stack frames and thread state, and evaluate expressions.

核验说明Verification notes

本条目 confidence: partial，原因如下。

已核验

支持的 IDE 宿主与最低版本
Plan mode、真调试器与 /demo 等能力
Action Allowlist 与 Brave Mode 的权限机制
MCP 仅 stdio
.aiignore 的边界
AI Free / Pro / Ultimate 的 credits 配额
「AI Enterprise 档不含 Junie」

未取到

上下文窗口与压缩参数
Junie Local 的完整适用范围

已核到的官方页：

jetbrains.com/junie/、/help/junie/（get-started、install、modes、 customize-guidelines、user-approval、aiignore、model-context-protocol-mcp、 models、licensing-and-subscriptions、diffs-and-review）、/ai-ides/buy/、 blog.jetbrains.com/junie/。

This entry is confidence: partial, for the following reasons.

Verified

Supported IDE hosts and minimum versions
Capabilities such as Plan mode, the real debugger and /demo
The permission mechanism of Action Allowlist and Brave Mode
MCP stdio-only
The boundary of .aiignore
Credits quotas of AI Free / Pro / Ultimate
"The AI Enterprise tier does not include Junie"

Not obtained

Context window and compaction parameters
The full applicability scope of Junie Local

Official pages verified on 2026-10-08:

jetbrains.com/junie/, /help/junie/ (get-started, install, modes, customize-guidelines, user-approval, aiignore, model-context-protocol-mcp, models, licensing-and-subscriptions, diffs-and-review), /ai-ides/buy/, blog.jetbrains.com/junie/.