JeecgBoot
【AI 时代的业务系统基座】企业级 AI 低代码平台：权限、多租户、工作流、报表、大屏、AI 知识库等通用能力开箱即用，AI 只需生成业务差异部分。AI Skills 一句话生成完整系统, 建表、前后端代码、菜单权限、BPM 流程、表单、报表、大屏全自动。内置 AI 应用平台（聊天、知识库、流程编排、MCP），兼容主流大模型。Java + Vue3，支持单体/微服务与信创国产化。
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 60 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
JeecgBoot 3.9.5 frontend builds and serves correctly with Vite 8/Vue 3; backend compiles all 29 Maven modules; unit tests for base-core (70 tests, 67 pass) and airag (1 pass, 0 fail) execute correctly. System-start integration tests remain blocked without MySQL/Redis containers.
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.
- Node.js 18 insufficient for Vite 8 / Node.js 20+ required5 minutes
- Java/Maven not pre-installed in container5 minutes
- pnpm 12 incompatible with lockfile; required pnpm 92 minutes
- jest-environment-jsdom missing (Jest 28+ change)1 minute
- Maven download URL 4041 minute
- 3 DnsResolution failures in SsrfFileTypeFilterTest (container has no DNS for cdn.example.com)1 minute
- Install time
- 60 minutes
- Cold machine to finish
- 50 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- Frontend: pnpm build produced dist/index.html (16.9KB); http-server on :3001 returned HTTP 200. Jest: 1 suite 1 test passed. Backend: mvn clean install built 29 modules SUCCESS; mvn test on base-core ran 70 tests (67 pass, 3 DNS failures); mvn test on airag ran 1 test passed.
- Model tokens used
- 103,692
- 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.
Here's the complete summary of my work on JeecgBoot 3.9.5. **What was done:** - **Frontend (Vue3 + Vite 8):** Installed Node.js 20.19.0 (container had 18), pnpm 9.15.9, all deps… - **Backend (Spring Boot 4 + Maven):** Downloaded JDK 17 and Maven 3.9.9 (none pre-installed). `mvn… - **Errors:** 3 failures in `SsrfFileTypeFilterTest` due to `cdn.example.com` DNS failure in contai… tokens used 103,692 Here's the complete summary of my work on JeecgBoot 3.9.5. **What was done:** - **Frontend (Vue3 + Vite 8):** Installed Node.js 20.19.0 (container had 18), pnpm 9.15.9, all deps… - **Backend (Spring Boot 4 + Maven):** Downloaded JDK 17 and Maven 3.9.9 (none pre-installed). `mvn… - **Errors:** 3 failures in `SsrfFileTypeFilterTest` due to `cdn.example.com` DNS failure in contai…
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 60 minutes.
- Recovered from all 7 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.
- Measured 2 times, so the result is not a one-off.
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 60 minutes, hitting 7 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. 2 attempts are 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.38: 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?
- 60 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?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for JeecgBoot?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.