d2-vscode
VSCode extension for D2 files.
Runs with mockssource: GitHubhomepageTypeScriptBSD-3-Clausecommit 23346fb575b1
TypeScript, BSD-3-Clause licensed. The project labels itself: diagram, diagramming and diagrams.
d2-vscode runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The VS Code extension installs, builds with webpack, packages into a working .vsix (3.29 MB), installs into VS Code 1.143.1, and activates with all 5 D2 commands registered. Syntax highlighting grammar regenerated from YAML source.
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 92 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.
- @vscode/vsce 4.x requires Node.js >=20, system Node is 181.5 minutes
- yq (YAML-to-JSON converter) not available for regenerating syntax grammar from YAML source1 minute
- vsce deps (undici) require File global not available in Node 180.5 minutes
- Install time
- 7 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- runTests extensionTestsPath with extension activated reported 'D2 commands: D2.ShowPreviewWindow, D2.CompileToSvg, D2.PickLayout, D2.PickTheme, D2.ToggleSketch'; also code --install-extension d2.vsix returned 'successfully installed' and code --list-extensions showed [email protected]
- Model tokens used
- 375,581
- Exact commit tested
- 23346fb575b1
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
"final_state": "The VS Code extension installs, builds with webpack, packages into a working .vsi… } exec /bin/sh -lc '# Calculate total elapsed time START=$(stat -c %Y /work/repo/README.md) NOW=$(date +%s) MINUTES=$(( (NOW - START) / 60 )) echo "Elapsed minutes: $MINUTES"' in /work/repo succeeded in 0ms: Elapsed minutes: 7 tokens used 375,581
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
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed BSD-3-Clause, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 7 minutes to install, slower than the median of the 13 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 14 diagram projects Argusic has installed and timed, d2-vscode was the 11th fastest to reach a running state, and 11 of 14 reached one at all.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.05 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/d2-vscode)Questions
- Does d2-vscode run?
- d2-vscode runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test d2-vscode?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 23346fb575b1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test d2-vscode?
- 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 d2-vscode take to install?
- 7 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 d2-vscode need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing d2-vscode?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does d2-vscode compare with the alternatives?
- Of the 14 diagram projects Argusic has installed and timed, d2-vscode was the 11th fastest to reach a running state, and 11 of 14 reached one at all.
- Where is the evidence for d2-vscode?
- 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.