wtp
🌳 A powerful Git worktree CLI tool with automated setup, branch tracking, and smart navigation
Runssource: GitHubhomepageGoMITcommit 842920d489e9
Go, MIT licensed. The project labels itself: cli, developer tools, git, git worktree, go, productivity and worktree.
wtp runs. An Argusic agent installed it in 25 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
wtp builds, installs, lints, and passes all unit and e2e tests, and its add/list/cd/exec/remove commands were verified against a real local git repository.
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.
- Default .wtp.yml hook runs `wtp list`, which exits 127 when wtp is not on PATH5 minutes
- go toolchain missing in container (go: not found)3 minutes
- Install time
- 25 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go tool task test exit 0 with all packages ok; go tool task test-e2e exit 0 (ok test/e2e 7.386s); wtp --version printed 'wtp version 842920d'; wtp add/list/cd/exec/remove exercised on a real git repo with expected output (worktree created at ../worktrees/feature/demo and removed cleanly); go tool task lint printed '0 issues.'
- Model tokens used
- 55,660
- Exact commit tested
- 842920d489e9
- 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.
tokens used 55,660 All verification is complete. Here is the report. **Summary** `wtp` builds, installs, and works end to end. The only gaps were environment ones, not project bugs… **What I ran and observed** - `go tool task build` — exit 0, produced `wtp` (4,128,952 bytes). - `go tool task test` — exit 0, all 8 packages `ok`, e2e 22.5s. - `go tool task test-e2e` — exit 0, `ok .../test/e2e 7.386s`, all subtests `PASS`. - `go tool task install` — exit 0, installed to `$GOBIN/wtp`; `wtp --version` → `wtp version 842920… - `go tool task lint` — exit 0, `0 issues.`; `fmt` clean (no diff). - Real demo: `wtp init` created `.wtp.yml`; `wtp add -b feature/demo` created `/tmp/wtp-demo2-12726…
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 2 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.
What did not, or is not known
- Took 25 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 128 cli projects Argusic has installed and timed, wtp was the 124th fastest to reach a running state, and 117 of 128 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/wtp)Questions
- Does wtp run?
- Yes. wtp runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test wtp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 842920d489e9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test wtp?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does wtp take to install?
- 25 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 wtp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing wtp?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does wtp compare with the alternatives?
- Of the 128 cli projects Argusic has installed and timed, wtp was the 124th fastest to reach a running state, and 117 of 128 reached one at all.
- Where is the evidence for wtp?
- 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.