Does claude-code-filetree run?

Yes. claude-code-filetree runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test claude-code-filetree?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 91080e6731e8. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test claude-code-filetree?

The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does claude-code-filetree take to install?

0.2 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 claude-code-filetree need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing claude-code-filetree?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for claude-code-filetree?

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.

claude-code-filetree

IDE-style file tree for Claude Code: a live pane that shows which files Claude reads and edits, with git status, diffs, content search, file previews and guarded paths, in the terminal and the Claude Desktop app.

Runssource: GitHubTypeScriptMITcommit 91080e6731e8

TypeScript, MIT licensed. The project labels itself: agentic coding, ai agents, ai coding, anthropic, claude, claude code, claude code plugin and claude desktop.

claude-code-filetree runs. An Argusic agent installed it in 0.2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The repository type-checks with tsc --noEmit reporting zero errors; the claude plugin test harness runs 247 tests across 2 files (open.test.ts and surfaces.test.tsx) with all passing; CI convention checks (greps.sh, version-test.sh) pass; the standalone regex script confirms 241 translated ERE patterns agree with grep -E and git grep -E.
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 90 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 90 / 100
cost of the verifying run: $0.04 (measured)
recorded runs: 2
last tested: 2026-11-05
stars: 369
forks: 0
open issues: 0
watchers: 0
created: -
last push: -

Subject data from GitHub, linked at the top of this page. 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.

Install time: under a minute
Cold machine to finish: 5 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: claude plugin test . exited 0, 247 passed, 0 failed
Model tokens used: 260,267
Exact commit tested: 91080e6731e8
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.

**Type check**: `tsc --noEmit` exits cleanly with zero errors.
**Tests**: `claude plugin test .` runs 247 tests across 2 files — all pass, 0 fail, in ~100s.
**CI scripts**: `scripts/ci/greps.sh` (coding convention checks) and `scripts/ci/version-test.sh` (…
**Standalone verification**: `scripts/check-ere.ts` confirms 241 regex patterns agree with `grep -E…
tokens used
260,267
Everything is clean. Let me compile all my findings.
**Install**: The project is a Claude Code plugin (mod). It has no `package.json` of its own — it's …
**Type check**: `tsc --noEmit` exits cleanly with zero errors.
**Tests**: `claude plugin test .` runs 247 tests across 2 files — all pass, 0 fail, in ~100s.
**CI scripts**: `scripts/ci/greps.sh` (coding convention checks) and `scripts/ci/version-test.sh` (…
**Standalone verification**: `scripts/check-ere.ts` confirms 241 regex patterns agree with `grep -E…

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.2 minutes, faster than the median of the 28 comparable projects Argusic has measured.
Nothing broke on the way: zero errors between clone and running.
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 29 agentic-coding projects Argusic has installed and timed, claude-code-filetree was the 3rd fastest to reach a running state, and 21 of 29 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.2 minutes after the clone.
Following its own README: the documented path worked with nothing to fix.

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	2/3	Runs	100.00	0.04	2026-11-05 11:06 UTC
Argusic Runner	1/3	Unverified	80.00	0.16	2026-11-05 10:32 UTC

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/claude-code-filetree.svg)](https://argusic.com/subject/claude-code-filetree)

Questions

Does claude-code-filetree run?: Yes. claude-code-filetree runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test claude-code-filetree?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 91080e6731e8. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test claude-code-filetree?: The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does claude-code-filetree take to install?: 0.2 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 claude-code-filetree need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing claude-code-filetree?: Nothing did, in the recorded run: zero errors between clone and running.
How does claude-code-filetree compare with the alternatives?: Of the 29 agentic-coding projects Argusic has installed and timed, claude-code-filetree was the 3rd fastest to reach a running state, and 21 of 29 reached one at all.
Where is the evidence for claude-code-filetree?: 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.