monaco-editor
A browser based code editor
Runssource: GitHubhomepageJavaScriptMITcommit fdf1ee75a63b
JavaScript, MIT licensed. The project labels itself: browser, editor, monaco editor, typescript and vscode.
monaco-editor runs. An Argusic agent installed it in 17 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Monaco Editor v0.57.0 ESM build succeeds via rollup; 86 grammar tokenization tests pass on Node 18 with JSDOM. The deprecated AMD/Vite build and the LSP client (rolldown) builds fail on Node 18 and require Node 20+. All 86 language grammar tokenization tests pass.
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.
- import.meta.dirname is Node.js 20+ feature; 4 config files + 1 lsp client config fail on Node 183 minutes
- [email protected] depends on html-encoding-sniffer which requires Node 20+; crashes test suite with ERR_REQUIRE_ESM2 minutes
- Missing globalThis.crypto in JSDOM environment — monaco-editor-core uses crypto.randomUUID at import time2 minutes
- npm test fails because test:grammars script in package.json has glob pattern in quotes preventing shell expansion1 minute
- @rolldown/binding-linux-x64-gnu optional dependency not installed for monaco-lsp-client rolldown build1 minute
- Install time
- 17 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npm run test exited 0, 86 tests passed (abap, apex, azcli, bat, bicep, cameligo, clojure, coffeescript, cpp, csharp, csp, css, cypher, dart, dockerfile, ecl, elixir, flow9, freemarker2 variants, fsharp, go, graphql, handlebars, hcl, html, ini, java, javascript, julia, kotlin, less, lexon, liquid, lua, m3, markdown, mdx, mips, msdax, mysql, objective-c, pascal, pascaligo, perl, php, pla, postiats, powerquery, powershell, protobuf, pug, python, qsharp, r, razor, redis, restructuredtext, ruby, rust, sb, scala, scheme, scss, shell, sol/solidity, aes/sophia, sparql, sql, st, swift, systemverilog, tcl, twig, typescript, typespec, vb, wgsl, xml, yaml, pgsql); ESM build completed (rollup output at out/monaco-editor/esm/)
- Model tokens used
- 325,412
- Exact commit tested
- fdf1ee75a63b
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
/bin/sh -lc 'echo "--- Time check ---" && date' in /work/repo succeeded in 0ms: --- Time check --- Sun Nov 1 19:26:01 UTC 2026 exec /bin/sh -lc "# Calculate elapsed time from the session start # Installation started around 19:09, it's now 19:26, so roughly 17 minutes echo \"Started ~19:09, now 19:26, about 17 minutes elapsed\"" in /work/repo succeeded in 0ms: Started ~19:09, now 19:26, about 17 minutes elapsed tokens used 325,412
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 5 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.
What did not, or is not known
- Took 17 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
Of the 10 browser projects Argusic has installed and timed, monaco-editor was the 9th fastest to reach a running state, and 8 of 10 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.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/monaco-editor)Questions
- Does monaco-editor run?
- Yes. monaco-editor runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test monaco-editor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fdf1ee75a63b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test monaco-editor?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does monaco-editor take to install?
- 17 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 monaco-editor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing monaco-editor?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does monaco-editor compare with the alternatives?
- Of the 10 browser projects Argusic has installed and timed, monaco-editor was the 9th fastest to reach a running state, and 8 of 10 reached one at all.
- Where is the evidence for monaco-editor?
- 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.