ide
✨ Simple, free and open-source online code editor.
Runssource: GitHubhomepageJavaScriptMITcommit 4e0e7a4bfe32
JavaScript, MIT licensed. The project labels itself: code editor, code execution, code executor, code runner, online compiler, online editor, online ide and online judge.
ide runs. An Argusic agent installed it in 0.3 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Judge0 IDE loads fully in Chrome: all CDN libraries, Monaco editors, GoldenLayout panels, theme toggle, and Puter AI API are available. The Judge0 Code Execution API responds with HTTP 200 'Accepted' for submitted C++ code. Only limitations are file:// protocol issues (favicons, service worker) and the inability to reach localhost via HTTP from Chrome in this container.
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.
- Chrome in this container cannot reach localhost (network namespace restriction), file:// protocol must be used instead22 minutes
- Favicon paths use absolute file paths (/favicons/...) that fail from file:// protocol
- ServiceWorker registration fails on file:// protocol (expected browser limitation)
- Puter.js warns about missing HTTP origin when served via file://
- Install time
- under a minute
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- Puppeteer (Chrome 121) loaded file:///work/repo/index.html with --disable-web-security; page.evaluate executed fetch to https://ce.judge0.com/submissions with C++ code, received 200 'Accepted' stdout='Hello Judge0' time=0.003s memory=1596KB; 71 languages from GET /languages; 3 Monaco editor models verified; all DOM elements present
- Model tokens used
- 328,612
- Exact commit tested
- 4e0e7a4bfe32
- 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.
- Puppeteer Chrome v121 loads the app via `file://` with `--disable-web-security` (localhost unreac… - **Real API call to Judge0 CE**: Submitted C++ code (`#include <iostream>` / `cout << "Hello Judge… - 71 programming languages fetched from `GET /languages` - 3 Monaco editor models instantiated (source/stdin/stdout), all CDN libraries loaded (jQuery, Mona… - 98 language options in the dropdown, theme toggle works (adjust → moon icon) - SQLite database (`data/db.sqlite`) is a valid Chinook sample database **Issues found (all non-critical):** 1. Chrome in this container can't reach localhost HTTP (RunPod network namespace) 2. Favicon paths fail from `file://` protocol 3. ServiceWorker registration fails on `file://` 4. Puter.js sign-in requires HTTP origin No code changes were needed — the repository works as-is.
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 0.3 minutes, faster than the median of the 11 comparable projects Argusic has measured.
- Recovered from all 4 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.
- Measured 2 times, so the result is not a one-off.
Of the 12 code-editor projects Argusic has installed and timed, ide was the 2nd fastest to reach a running state, and 11 of 12 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 0.3 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
Topics (from GitHub)
code-editorcode-executioncode-executorcode-runneronline-compileronline-editoronline-ideonline-judgeweb-ide
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ide)Questions
- Does ide run?
- Yes. ide runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test ide?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4e0e7a4bfe32. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ide?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ide take to install?
- 0.3 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 ide need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ide?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ide compare with the alternatives?
- Of the 12 code-editor projects Argusic has installed and timed, ide was the 2nd fastest to reach a running state, and 11 of 12 reached one at all.
- Where is the evidence for ide?
- 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.