netbeans
Apache NetBeans
Runssource: GitHubhomepageJavaApache-2.0commit 4d2a85c0e270
Java, Apache-2.0 licensed. The project labels itself: code editor, ide, java, netbeans and netbeans platform.
netbeans runs. An Argusic agent installed it in 27 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Apache NetBeans builds from source, all 64 platform unit tests pass, and the IDE CLI starts and lists modules successfully using JDK 21 and Ant 1.10.18.
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.
- JDK 21+ not installed in container1 minute
- Apache Ant not installed in container1 minute
- Install time
- 27 minutes
- Cold machine to finish
- 31 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- ant -Dcluster.config=platform test-platform exited 0 with 64 tests, 0 failures, 0 errors; and timeout 45 netbeans --modules --list --userdir /tmp/nb-test-userdir2 printed IDE version and module list
- Model tokens used
- 131,126
- Exact commit tested
- 4d2a85c0e270
- 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.
2026-10-01T19:47:47.979647Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-10-01T19:47:47.979657Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… tokens used 131,126 All tasks completed. Here's the summary: - **JDK 21 (Adoptium Temurin)** downloaded and extracted to `/tmp/jdk-21.0.12.1+1` - **Apache Ant 1.10.18** downloaded and extracted to `/tmp/apache-ant-1.10.18` - **Platform build** (`ant -Dcluster.config=platform build-nozip`) — SUCCESS - **Full release build** (`ant build`) — SUCCESS, produced 491MB zip - **Platform tests** (`ant -Dcluster.config=platform test-platform`) — **64 tests, 0 failures, 0 er… - **App CLI** launched via `netbeans --help` and `netbeans --modules --list` — both worked, showing… No real third-party credentials were needed; no mocks were required. No system packages had to be i…
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 27 minutes.
- 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 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.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/netbeans)Questions
- Does netbeans run?
- Yes. netbeans runs. Argusic installed and launched it on a clean machine in 27 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test netbeans?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4d2a85c0e270. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test netbeans?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does netbeans take to install?
- 27 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 netbeans need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing netbeans?
- 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.
- Where is the evidence for netbeans?
- 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.