JeecgBoot
【低代码v2.0，一句话即可生成整个系统】企业级AI低代码平台，一键生成前后端代码甚至整个系统。 AI Skills 一句话画流程、设计表单、生成报表、大屏。内置 AI应用平台涵盖：AI聊天、知识库、流程编排、MCP插件等，兼容主流大模型。引领AI低代码「Skills 生成 → 在线配置 → 代码生成 → 手工合并->AI修改」开发模式，解决 Java 项目 90% 重复工作，提高效率又不失灵活。
Runssource: GitHubhomepageJavaApache-2.0commit 87d7f938d47d
Java, Apache-2.0 licensed. The project labels itself: activiti, agent, ai, antd, claude code, cli, codegenerator and codex.
JeecgBoot runs. An Argusic agent installed it in 54 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Java backend compiles (Spring Boot 4.1.0, Maven multi-module), 67 of 70 unit tests pass (SSRF, SQL injection, IP utility), and the Vue 3 frontend builds to a deployable dist/ directory
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- pnpm 12 requires allowBuilds config in pnpm-workspace.yaml for postinstall scripts3 minutes
- No Java JDK installed in container2 minutes
- pnpm lockfile had stale npmmirror tarball URLs causing policy rejection2 minutes
- Node.js 18.19.1 lacks `styleText` export from node:util needed by Vite 8 / rolldown2 minutes
- No Maven installed in container1 minute
- No pnpm available1 minute
- Install time
- 54 minutes
- Cold machine to finish
- 55 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- Backend: `mvn compile -DskipTests -pl jeecg-boot-base-core,jeecg-module-system/jeecg-system-biz,jeecg-module-system/jeecg-system-start -am` exited 0 BUILD SUCCESS; `mvn test -pl jeecg-boot-base-core -am -DskipTests=false` ran 70 tests, 67 passed, 3 failed (all DNS resolution in isolated container); Frontend: `pnpm build` produced dist/index.html and exited 0
- Model tokens used
- 992,583
- Exact commit tested
- 87d7f938d47d
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:159)
at org.junit.jupiter.api.AssertDoesNotThrow.createAssertionFailedError(AssertDoesNotThrow.java:90)
<failure message="Unexpected exception thrown: org.jeecg.common.exception.JeecgBootException: 非…
at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:159)
at org.junit.jupiter.api.AssertDoesNotThrow.createAssertionFailedError(AssertDoesNotThrow.java:90)
<failure message="Unexpected exception thrown: org.jeecg.common.exception.JeecgBootException: 非…
at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:159)
at org.junit.jupiter.api.AssertDoesNotThrow.createAssertionFailedError(AssertDoesNotThrow.java:90)
All data collected. Here is the final result:
tokens used
992,583
All data collected. Here is the final result:Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 54 minutes.
- Recovered from all 8 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
activitiagentaiantdclaude-codeclicodegeneratorcodexflowablelangchain4jllmlow-codemcpmybatis-plusragskillsspring-aispringbootspringcloudvue3
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jeecgboot)Questions
- Does JeecgBoot run?
- Yes. JeecgBoot runs. Argusic installed and launched it on a clean machine in 54 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test JeecgBoot?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 87d7f938d47d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test JeecgBoot?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does JeecgBoot take to install?
- 54 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does JeecgBoot need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing JeecgBoot?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for JeecgBoot?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.