Jaipilot

JAIPilot helps Codex and Claude Code research maintainer intent, clean, test, review, safely upgrade dependencies and JDKs, and optimize real Java repositories without drifting into unnecessary code or unproved changes.

By default, your agent runs Java builds, tests, analysis, profiling, and benchmarks on a ready remote Java machine whenever the task does not require laptop-only access or state.

JAIPilot does not replace your coding agent or add another AI. It gives your agent focused Java workflows, remote compute, and one rule: show evidence, not confidence.

Further reading: Preventing agent drift: A guide to shipping serious code via vibe-coding explains the engineering principles behind JAIPilot's bounded, evidence-first workflows.

Install and run

Codex

JAIPilot is packaged for the official OpenAI plugin directory. Once the listing is approved, install it there to get all eight local skills and the optional OAuth remote MCP together. The same public MCP remains available as a direct connection:

codex mcp add jaipilot --url https://api.jaipilot.com/functions/v1/jaipilot/mcp

Claude Code

/plugin marketplace add JAIPilot/jaipilot
/plugin install jaipilot@jaipilot

Any MCP client

If your client supports remote HTTP MCP servers and OAuth, connect directly to JAIPilot without installing a plugin or running a local process:

https://api.jaipilot.com/functions/v1/jaipilot/mcp

Clients that use the common mcpServers configuration shape can add:

{
  "mcpServers": {
    "jaipilot": {
      "type": "http",
      "url": "https://api.jaipilot.com/functions/v1/jaipilot/mcp"
    }
  }
}

Complete the OAuth sign-in when the client first connects. Clients with MCP Skills support can discover the JAIPilot skills directly; tool-only clients can load the same versioned instructions through the read-only skill_get tool. Remote execution remains opt-in and requires approval before an exact committed repository revision is uploaded.

GitHub Marketplace

Install the JAIPilot GitHub App to repair failed Dependabot and Renovate pull requests for Maven and Gradle repositories.

See what JAIPilot changed

JAIPilot does not hide its value behind skill routing or build logs. Every meaningful skill milestone uses the same restrained, one-line grammar:

**JAIPilot · <capability>** — <completed outcome>; <strongest fresh proof>.

For example: JAIPilot · Test generation — 7/7 focused tests passed; fresh line and branch coverage reached 100%.

The update appears only after completed work, never for intent or routing. When completion coincides with the final response, the same line becomes its outcome lead and is immediately followed by one consolidated impact section. Nested skills contribute to that section instead of printing a stack of banners.

For example, a measured Petclinic test-generation run ends with evidence in this shape:

JAIPilot · Test generation — 10 useful tests added; changed-method line and branch coverage reached 100%.

JAIPilot impact

• Test generation: 75 → 85 tests (+10); changed-method line and branch coverage 0% → 100% (+100 percentage points)
• Evidence: ./mvnw -q clean verify — 85/85 tests passed

Impact uses fresh, same-scope before/after evidence already useful to the task. When a comparison is not available, JAIPilot says not measured; when the value is a maintainer decision or rejected unsafe change, it describes that outcome without inventing hours saved, risk percentages, or a counterfactual “without JAIPilot” score.

Example prompts

Open a Java repository and ask JAIPilot the same way you would ask a teammate. Each example shows the skills JAIPilot selects and why that workflow helps.

Check whether an issue is worth picking up

Prompt