JAIPilot/ Docs

Set up JAIPilot in IntelliJ IDEA

Install the plugin, connect Codex or Claude Code, and run a job from the Jobs tool window.

Install JAIPilot ↗
01

Install and connect

Follow these steps in IntelliJ IDEA. You can use an existing Codex or Claude Code login.

  1. 01

    Install JAIPilot

    Settings → Plugins → Marketplace

    Search for JAIPilot and install the plugin in IntelliJ IDEA.

  2. 02

    Sign in to JAIPilot

    Settings → JAIPilot

    Choose Sign in to JAIPilot to start your account trial.

  3. 03

    Connect Codex or Claude Code

    Settings → JAIPilot → Coding agent

    Install Node.js 22+, then sign in to Codex or Claude Code. JAIPilot starts the local adapter and reuses your provider settings; no separate agent CLI is required.

  4. 04

    Run a job

    JAIPilot tool window → Jobs → New

    Choose a workflow, or start from Java code in the editor's JAIPilot menu.

  5. 05

    Inspect the result

    JAIPilot tool window → Jobs

    Read the checks and changed files. Open the IntelliJ diff before keeping or undoing edits.

02

Watch a job

These captures show a Minimize Code proposal being reviewed and verified, followed by a Verify Change job.

JAIPilot reviewing, applying, undoing, redoing, and verifying a Minimize Code proposal
Minimize Code Compare a proposal, inspect the diff, apply it, and run verification.
JAIPilot running Verify Change and showing passing tests and coverage in IntelliJ IDEA
Verify Change Watch the build and tests run, then read the coverage result.
JAIPilot settings for connecting a local coding agent Connect your agent ↗JAIPilot workflow choices inside IntelliJ IDEA Choose a workflow ↗JAIPilot verification results showing checks and coverage Read the evidence ↗JAIPilot change record in IntelliJ IDEA Review the change record ↗
03

Workflow reference

Choose a job by what you have now and the result you need.

Implement Jira Issues

Jira issue

One-shot implementation, diff, and checks

Implement GitHub Issues

GitHub issue

One-shot implementation, diff, and checks

Review PRs

GitHub pull request

Review findings to inspect and publish

Fix PR Comments

Selected review threads

Fixes and rerun checks

Safely Clean Code

Unused-code findings

Removal diff and remaining findings

Minimize Code

A Java class or repository

Proposals, diff, and verification

Dependency Doctor

Maven or Gradle dependencies

Repair or upgrade dependencies with compatibility evidence

Fix IntelliJ Findings

Selected inspection findings

Before and after inspection counts

Repair Build Failure

Failing Maven or Gradle build

Repair diff and rerun result

Generate Tests

Java classes or repository

Tests and JaCoCo coverage when available

Fix Tests

Failing tests

Test fixes and rerun result

Stabilize Flaky Tests

Suspected flaky test

Reproduction and rerun evidence

Verify Change

Current project changes

Build, tests, coverage, and inspections

Dependency Doctor helps repair or upgrade dependencies; Minimize Code simplifies code. Both keep a completed assessment until you select Recalculate. Opening a saved result does not run the assessment again.

04

Results and history

Jobs keeps the conversation, checks, and changed-file list together. Open a diff in IntelliJ before keeping or undoing an edit. A job can finish without changing code.

Analysis records coverage, IntelliJ findings, and PR or issue outcomes by repository and branch. Prompts, diffs, and terminal logs are not synced to the account dashboard.

Open Analysis →

Install JAIPilot

Open the plugin listing in JetBrains Marketplace.

IntelliJ plugin ↗