Junie still sees the names of files in .aiignore, and Brave mode or an allowlisted command can read them without asking. Its non-interactive sessions also trust a project automatically and load the project's MCP servers and hooks with no prompt. Settle these and each sign-in's data path before security signs off. Every fact here is from JetBrains' documentation as of October 12, 2026.
When you need this
- Security asks what Junie can execute and delete on a developer laptop.
- Some repositories hold secrets or client code that no third-party model may see.
- Junie is about to run in CI with write access to repositories.
- Legal asks whether JetBrains or its model providers keep or train on your code.
Evaluation criteria
Standardize approvals
What runs without a person approving it?
Look forPublish an allowlist and Brave mode policy. Junie CLI's ~/.junie/allowlist.json covers five action types, including executables, MCP tools, edits outside the project, and reads of files that may hold secrets. The default is ask. CLI Brave mode levels are Off, Auto, and On. AI Chat uses Safe, Auto, and Brave. OS-level sandbox mode is in JetBrains' Early Access Program: it needs the Early Access version of Junie CLI, runs on macOS and Linux only, and starts off in each new session unless launched with --sandbox. Release builds keep it off.
Protect sensitive files
Which files must Junie ask before reading or editing?
Look forAdd sensitive files to a root .aiignore using .gitignore syntax. Junie asks before viewing or editing them but still sees their names. Brave mode and allowlisted commands that reference the files bypass that prompt. JetBrains' agent table says Claude Agent, Codex, and GitHub Copilot in AI Chat do not respect .aiignore.
Trust only known projects in automation
Which project configuration loads without a prompt?
Look forRun headless Junie only on repositories you control. Interactive CLI sessions ask before trusting a project. Non-interactive sessions, including one-shot prompts, piped input, and ACP, trust it automatically. They load its MCP servers, hooks, agents, skills, and guidelines without asking. The Junie GitHub Action runs on your GitHub runners.
Map the data path per sign-in
Where do prompts and code go for each way engineers sign in?
Look forCheck the data path for each sign-in. JetBrains AI sends prompts and code context to the model provider. JetBrains states it does not work with providers that train on customer data. It retains nothing unless detailed data collection is enabled, then keeps data for up to a year. On company licenses, administrators control that setting, which defaults to off. Junie Lite uses JetBrains infrastructure only. Your own keys send requests under your provider agreement. Remote mode streams a CLI session through the Junie web app and is unavailable with AI Enterprise sign-in.
Pick the enterprise boundary
Does any model traffic have to stay inside your network?
Look forUse AI Enterprise through IDE Services when traffic must avoid JetBrains AI. It supports Azure OpenAI, the OpenAI Platform, and Amazon Bedrock. For air-gapped use, connect an on-premises OpenAI-compatible server such as vLLM or llama.cpp. Log requests and responses to your object storage. JetBrains Central lists Enterprise audit logs and hybrid deployments as coming soon.
Questions to ask vendors
- Which builds of Junie CLI do engineers run, and does any team rely on sandbox mode?
- Which repositories need an .aiignore before Junie is enabled?
- Is detailed data collection off for our organization, and who can change it?
- Which pipelines run Junie, with which token scopes and on whose runners?
Red flags
- Brave mode On on laptops that hold production credentials.
- Secrets protected by .aiignore alone, with allowlisted commands that can read them.
- Headless Junie runs on pull requests from forks or untrusted repositories.
- Detailed data collection on a company license set centrally by admins and never checked in the organization's admin console.
Products in this piece
Sources
- Official documentation
- 17
- Public source
- 2
- Junie docs: Action Allowlist in Junie CLI
- Junie docs: Action Allowlist in the IDE plugin
- Junie docs: Junie CLI quickstart
- JetBrains AI docs: Junie by JetBrains in AI Chat
- Junie docs: Junie IDE plugin
- JetBrains AI docs: Agents
- Junie docs: Headless mode
- Junie docs: Junie GitHub Action
- JetBrains AI FAQ
- JetBrains AI docs: Data handling
- Junie docs: Junie Lite
- Junie docs: Remote mode
- IDE Services docs: Manage AI Enterprise
- IDE Services docs: AI Enterprise in isolated infrastructure
- IDE Services docs: Logging of AI requests
- JetBrains Central Console docs: Plans and pricing
- JetBrains Central Console docs: AI policies
- Vortelf on Reddit r/Jetbrains: Junie is disappointing (Jun 5, 2025)
- bb88 on Hacker News: Junie in Brave mode applies changes before review (Apr 30, 2025)