ai-git-bot

The self-hosted AI workflow automation platform for Git repositories.

Runssource: GitHubJavaMITcommit d1e8b3b5b52c

Java, MIT licensed. The project labels itself: ai, ai tools, anthropic, automation, bitbucket, bot, chatbot and code review.

ai-git-bot runs. An Argusic agent installed it in 9 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The ai-git-bot Spring Boot application v1.31.0 compiles, all 4032 unit tests pass, and the app starts up serving the health endpoint at HTTP 200 on port 8080 with H2 file-based database and Flyway migrations applied.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.05 (measured)
recorded runs
1
last tested
stars
202
forks
0
open issues
0
watchers
0
created
-
last push
-

Subject data from GitHub, linked at the top of this page. 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.

Time lost to each failure while testing ai-git-bot, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Missing Java 21 JDK and Maven in container2 minutes
  • Missing OpenSSH client tools (ssh-keygen, ssh-keyscan)2 minutes
Install time
9 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
mvn test exited 0, 4032 passed, 0 failures, 0 errors, 9 skipped; curl localhost:8080/actuator/health returned HTTP 200; curl localhost:8080/ returned HTTP 302 (redirect to /setup as expected for fresh install)
Model tokens used
60,994
Exact commit tested
d1e8b3b5b52c
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Now let me compute the total time and produce the final report.
**Timeline:**
- 07:16: Start of session
- 07:17: Downloaded JDK
- 07:17: Downloaded Maven
- ~07:19: First test run
- 07:20-07:22: Fixed missing SSH tools
- 07:25: Tests all pass & app verified
Total elapsed: ~9 minutes.
2026-11-21T07:25:18.395630Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce…
tokens used
60,994

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.
  • Recovered from all 2 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 MIT, as reported by its host.

What did not, or is not known

  • Took 9 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 237 ai projects Argusic has installed and timed, ai-git-bot was the 165th fastest to reach a running state, and 168 of 237 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 9 minutes after the clone.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.05

Topics (from GitHub)

aiai-toolsanthropicautomationbitbucketbotchatbotcode-reviewdevopsgiteagithubgitlabjavallama-cppllmollamaopenaipull-requestself-hostedspring-boot

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/ai-git-bot.svg)](https://argusic.com/subject/ai-git-bot)

Questions

Does ai-git-bot run?
Yes. ai-git-bot runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test ai-git-bot?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d1e8b3b5b52c. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ai-git-bot?
The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ai-git-bot take to install?
9 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 ai-git-bot need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ai-git-bot?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does ai-git-bot compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, ai-git-bot was the 165th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for ai-git-bot?
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.

Discussion