floorplan

See how your app actually fits together. An interactive, plain-English map of your codebase, drawn by Claude or Codex.

Runssource: GitHubhomepageJavaScriptMITcommit 1ab7e19c8772

JavaScript, MIT licensed. The project labels itself: ai coding, architecture diagram, claude, claude code, claude code plugin, codebase visualization, codex and codex plugin.

floorplan runs. An Argusic agent installed it in 0 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm test passes all 371 tests, the scan and build scripts run on sample projects, and the map server serves the page at HTTP 200.

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.07 (measured)
recorded runs
2
last tested
stars
4,604
forks
379
open issues
35
watchers
10
size
7 MB
created
last push

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.

Time lost to each failure while testing floorplan, 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.

  • test failure: 'files of unclosed lists and brackets are still read quickly' asserted <2000ms but 'route objects nested deep (1.0 MB)' took 2213ms under full suite load5 minutes
Install time
under a minute
Cold machine to finish
14 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
node --test exits 0 with 371 pass, 1 skip, 0 fail; node skills/floorplan/scripts/scan.mjs and build.mjs succeeded on a sample project; curl http://127.0.0.1:4378/ returned 200
Model tokens used
65,780
Exact commit tested
1ab7e19c8772
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 2, 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.

 succeeded in 96344ms:
# duration_ms 96360.694718
The full suite takes ~96 seconds. The tests all pass.
Now let me compile my final result:
**Error encountered:** 1 test failure in `tests/hostile-content.test.mjs:559` — test "files of uncl…
Other than that, the repo installed and works out of the box — Node.js 18.19.1 is already present, …
tokens used
65,780
The full suite takes ~96 seconds. The tests all pass.
Now let me compile my final result:
**Error encountered:** 1 test failure in `tests/hostile-content.test.mjs:559` — test "files of uncl…
Other than that, the repo installed and works out of the box — Node.js 18.19.1 is already present, …

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 minutes, faster than the median of the 6 comparable projects Argusic has measured.
  • Recovered from all 1 error 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 7 ai-coding projects Argusic has installed and timed, floorplan was the 1st fastest to reach a running state, and 6 of 7 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 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 Runner2/3Runs100.000.07
Argusic Runner1/3Runs100.000.04

Topics (from GitHub)

ai-codingarchitecture-diagramclaudeclaude-codeclaude-code-plugincodebase-visualizationcodexcodex-plugindeveloper-toolsonboardingopenaivibe-coding

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/floorplan.svg)](https://argusic.com/subject/floorplan)

Questions

Does floorplan run?
Yes. floorplan runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test floorplan?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1ab7e19c8772. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test floorplan?
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 floorplan take to install?
0 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 floorplan need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing floorplan?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does floorplan compare with the alternatives?
Of the 7 ai-coding projects Argusic has installed and timed, floorplan was the 1st fastest to reach a running state, and 6 of 7 reached one at all.
Where is the evidence for floorplan?
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.

Discussion