JAIPilot

io.github.JAIPilot由 GitHub 账号 JAIPilot 发布v7.2.1更新于 Oct 24, 2026

Ship better Java with your coding agent.

发布方自己的服务:QuickBooks Connector by Meridian

已验证Streamable HTTP可网页运行开发者工具AI 与机器学习

概览

AI 生成的概览

JAIPilot 是一项 Java 测试服务,让编码代理为 Java 仓库生成、修复并验证单元测试,并提升行覆盖率。

可以做什么
为选定的类、路径或代码行生成、修复并稳定单元测试,包含有意义的断言和失败路径覆盖(generate_tests、fix_tests、stabilize_flaky_tests)。将实测行覆盖率提升至 90% 以上目标,并提供 100% 覆盖率工作流(improve_coverage、coverage_100)。只测试当前改动,或在重构前用特征测试锁定现有行为并在之后验证基线(test_current_changes、lock_behavior、verify_behavior)。检查项目的代码、构建与测试框架,然后运行针对性测试、回归测试套件和新的覆盖率报告。
适用场景
适用于编码代理处理 Java 代码库时,希望比代理单独生成更快、覆盖率更高的测试,或在重构前建立行为基线。它是叠加在现有代理之上的可选工具,而非替代品。
运行要求
需要 JAIPilot 账户(含订阅和额度),并通过 CLI 登录。需要 Git、JDK 和项目的构建工具;构建需包含 mcp 命令,并以仓库路径启动。测试和命令在本地运行,服务通过网络访问。
安装前请注意
选定的源代码、项目上下文和命令输出会发送到 JAIPilot 托管服务和模型提供商。工作流会修改仓库中的测试文件,接受改动前请查看结果和 git diff。使用会消耗 JAIPilot 额度,本地命令默认超时为一小时。

安装

在 SourceWeft 中

  1. 打开 控制台中的 JAIPilot,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.JAIPilot%2Fjaipilot/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

README

[JAIPilot]

JAIPilot — faster Java testing, stronger coverage, fewer bugs

Make your tests bulletproof.
~5× faster testing.
Enterprise grade unit tests. A 90%+ line coverage target.

Your Java testing specialist—straight from the terminal. Generate, repair, and verify tests. Fewer prompts. Stronger assertions.

Optimized for outcomes. Choose an outcome. Select your code. Get verified tests. Start with the CLI. Add MCP when you want JAIPilot inside your coding agent.

Download CLI · Get started · MCP setup · JAIPilot.com

See it run

Apache Kafka

[Actual Terminal recording of JAIPilot improving Apache Kafka's Deadline and LockUtils tests from 34.3% to 97.1% line coverage]

34.3% → 97.1% line coverage for two classes in 1m 53s. Added 13 tests; all 949 module tests passed.

Spring Petclinic — 100% coverage

[Actual Terminal recording of JAIPilot's coverage_100 workflow on Spring Petclinic, from 85.7% to 100% line coverage in 3m 21s]

85.7% → 100% line coverage across the project in 3m 21s. Added 36 tests with coverage_100; all 111 tests passed.

Production code preserved. Actual Terminal recordings; GIFs shorten idle waits. Reported times are full job durations with warm build caches; results vary. Commands, recordings, and full measurements →

How it works

Frontier LLM reasoning. Optimized testing tools. Prompts tailored to each outcome. Parallel workers in the managed service. Independent class tasks can run concurrently; local execution uses your toolchain and supported hardware parallelism.

  1. Inspect your code, build, and test framework.
  2. Generate or repair tests for behavior, boundaries, and failure paths, with meaningful assertions.
  3. Verify with focused tests, the final regression suite, and fresh coverage reports when configured.

90%+ line coverage target for generate_tests, improve_coverage, and lock_behavior, measured in selected production code when coverage is configured. Gaps and blockers are reported. Behavior baselines must pass before edits.

OutcomeWorkflow
Generate unit testsgenerate_tests
Improve coverageimprove_coverage
Fix failing testsfix_tests
Stabilize flaky testsstabilize_flaky_tests
Test current changestest_current_changes
Lock behavior before a refactorlock_behavior
Target 100% line coveragecoverage_100

Install

Requires Git, a JDK, and your project's build tools.

macOS / Linux

bash
curl -fsSL https://raw.githubusercontent.com/JAIPilot/jaipilot/main/install.sh | sh

Windows (PowerShell)

powershell
irm https://github.com/JAIPilot/jaipilot/releases/latest/download/install.ps1 | iex

npm

bash
npm install -g jaipilot

Homebrew (macOS / Linux)

bash
brew install JAIPilot/tap/jaipilot

Sign in, then run inside your Java repository:

bash
jaipilot auth loginjaipilot run improve_coverage --class com.acme.OrderService

Same JAIPilot account, subscription, and credits. Automatic update checks before workflows.

Install paths, manual updates, and troubleshooting →

Use the CLI

bash
jaipilot run generate_tests --class com.acme.OrderServicejaipilot run test_current_changes --alljaipilot run lock_behavior --path src/main/java/com/acme

Scope: whole repository, classes, paths, or selected lines. Review the result and git diff before accepting changes.

For a fresh, verified coverage target on a single-module Maven project:

bash
jaipilot run improve_coverage --all --coverage-target 80

The Maven adapter also provides local coverage checks and generation:

bash
./mvnw com.jaipilot:jaipilot-maven-plugin:1.2.1:check -Djaipilot.coverage.line=80./mvnw com.jaipilot:jaipilot-maven-plugin:1.2.1:run -Djaipilot.coverage.line=80

The Maven adapter 1.2.1 is published on Maven Central. Use mvnw.cmd in Windows PowerShell. Adapter setup, class/branch targets, and supported JaCoCo rules →

All commands, scopes, JSON output, and exit codes →

Why use JAIPilot if my coding agent already writes tests?

Fast testing. High coverage. Stronger tests. Less work for your coding agent.

  • ~5× faster testing than a general coding agent. Optimized prompts, tools, and parallel workers carry the testing workflow. Actual runtime varies by project. CLI examples: 97.1% coverage in 1m 53s on Kafka; 100% in 3m 21s on Petclinic.
  • 90%+ line coverage target. Meaningful assertions for selected behavior, boundaries, and failure paths, measured with your configured coverage tools.
  • Stronger regression protection. Lock behavior before edits; verify the original tests afterward. Our paired Codex example's saved tests caught 7/10 injected faults vs 3/10 with Codex alone.
  • Token efficiency. Offload test planning, generation, and repairs to JAIPilot's optimized service. This can reduce your coding agent's testing context, token use, and costs; JAIPilot credits apply.

Measured example: Codex with JAIPilot

Same refactor. Two fresh Codex sessions. Two Kafka utility classes. The MCP session used JAIPilot automatically, with no repository instruction file or extra testing prompt.

Saved regression suiteCodex aloneCodex + JAIPilot
Passing JUnit tests316
Line coverage of the selected Deadline class47.1%100%
Line coverage across both fixture classes40%65.7%
Branch coverage across both fixture classes30%80%
Injected faults caught by the saved tests3/107/10

13 more reusable tests. Four more deliberately introduced bugs caught. Same model, settings, initial tests, and warm build caches. One paired example; results vary.

The 90% target applies to selected code. Deadline: 100% (17/17 lines). The combined 65.7% (23/35) includes untargeted LockUtils, unchanged at 6/18 covered lines.

Method, evidence, and reproduction →

MCP for coding agents

Optional: make Codex, Claude Code, or another MCP agent better at Java testing. Give it a tested baseline before edits and real failures to guide repairs.

  1. Lock: lock_behavior creates and runs characterization tests before production edits, targeting 90%+ line coverage when configured.
  2. Edit: Your coding agent changes production code. Baseline tests stay unchanged.
  3. Verify: verify_behavior reruns the original baseline. Your agent investigates failures and repairs unintended changes before finishing.

Passing tests protect the behavior they exercise. Review old expectations for intentional behavior changes.

Codex

bash
codex mcp add jaipilot -- jaipilot mcp --repo /absolute/path/to/java-repository

Claude Code

bash
claude mcp add --transport stdio jaipilot -- jaipilot mcp --repo /absolute/path/to/java-repository

Start a new agent session. MCP instructions and tool descriptions include the workflow. No repository instruction file required. Tests and commands run locally. Jobs run in the background; 1 hour per local command by default.

Requires a build with the mcp command. Source setup, tool contracts, and timeout options →

Local execution and privacy

Builds and tests run locally. Selected source, project context, and command output go to JAIPilot's managed service and model provider. Sign-in credentials stay local with user-only permissions.

Privacy details · Ask a question · Report an issue · Report a vulnerability privately

MIT License · JAIPilot.com

来源:README.md,提交 d3fc8bc

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v7.2.1最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Pilot 集成