Yes. mtab runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test mtab?

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

What did it cost to test mtab?

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 mtab take to install?

4 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 mtab need a GPU?

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

What goes wrong when installing mtab?

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

Where is the evidence for mtab?

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.

mtab

🌴 lightweight new tab page extension

Runssource: GitHub homepageTypeScriptMITcommit 405f74d70c8d

TypeScript, MIT licensed. The project labels itself: chrome, chrome extension, extension, firefox, newtabpage and startpage.

mtab runs. An Argusic agent installed it in 4 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

bun install resolves 295 packages, tsc typechecks without errors, `bun run check` passes all 4 stages (format/lint/typecheck/test), and both Chrome and Firefox production builds produce complete dist/ directories with valid manifest.json files
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.01 (measured)
recorded runs: 2
last tested: 2026-09-19
stars: 573
forks: 18
open issues: 1
watchers: 3
size: 69 MB
created: 2024-03-09
last push: 2026-09-19

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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: 4 minutes
Cold machine to finish: 4 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: bun run check exited 0, format:check (passed), oxlint (passed, 0 warnings denials), tsc --noEmit (passed), bun test (14/14 passed, 10723 expect() calls). Chrome build: bun run build:chrome -> dist/ with manifest.json, index.html, JS/CSS bundles. Firefox build: bun run build:firefox -> similar dist/ with Firefox-specific manifest.
Model tokens used: 28,529
Exact commit tested: 405f74d70c8d
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.

 14 pass
 0 fail
 10723 expect() calls
Ran 14 tests across 1 file. [23.00ms]
exec
/bin/sh -lc 'export PATH="$HOME/.local/bin:$PATH" && cd /work/repo && cat EXTENSION_VERSION.txt' in…
 succeeded in 0ms:
1.12.9
All clear. Everything passes. Here's my report:
tokens used
28,529
All clear. Everything passes. Here's my report:

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 4 minutes.
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.

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 4 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.01	2026-09-19 07:19 UTC
Argusic Runner	2/3	Runs	100.00	0.01	2026-09-05 05:00 UTC

Topics (from GitHub)

chrome chrome-extension extension firefox newtabpage startpage

Embed the badge

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

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

Questions

Does mtab run?: Yes. mtab runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test mtab?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 405f74d70c8d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test mtab?: 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 mtab take to install?: 4 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 mtab need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing mtab?: Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for mtab?: 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.