The outcome
Create useful, auditable Junie behavior for a team while keeping secrets, side effects, and final decisions controlled.
Junie is a JetBrains coding agent for IDE, terminal, and automated review workflows. Exploring a codebase, producing an implementation plan, making supervised changes, and reviewing local or pull-request diffs with durable project guidance. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.
Before you begin
Set the boundary before the tool starts.
Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.
AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.
Step by step
A workflow you can repeat.
- 01
Inventory stable architecture rules, canonical commands, sensitive paths, review severity, provider policy, owners, and actions that always require a person.
- 02
Write concise .junie guidelines and .aiignore rules, linking canonical documentation and excluding credentials, generated data, and unnecessary private content.
- 03
Configure project defaults and review automation with minimal tools, read-only review intent, pinned dependencies, protected secrets, and no deployment capability.
- 04
Test normal changes, known defects, false positives, hostile repository text, forked pull requests, build-script edits, broad regex matches, and provider failures.
- 05
Require file-and-line evidence, keep merge decisions human-owned, audit logs and usage, and review trust, allowlists, guidelines, and workflows after each upgrade.
Working standard
What good use looks like.
- Keep durable guidance concise.
- Give review automation no release authority.
- Test hostile repository content.
Junie can edit files, run terminal commands, invoke MCP tools, read or write outside a project, load project configuration, and operate headlessly. Brave mode removes approval gates; broad regular expressions and action-type rules can authorize much more than intended; build-script edits may execute code. Review project trust, `.junie` configuration, `.aiignore`, guidelines, hooks, credentials, provider terms, and every allowlist rule before consequential work.
Official references
Check the current product documentation.
Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.