magnitude
Open source inference engine for the hardware you already own. Profiles your machine, recommends the best open models for it, and tunes them for your exact hardware. Works on Apple Silicon, NVIDIA, AMD, or nothing but a CPU.
Runssource: GitHubRustApache-2.0commit b3e5a06bda3e
Rust, Apache-2.0 licensed.
magnitude runs. An Argusic agent installed it in 25 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.
Magnitude CLI 0.2.0-alpha.1 installs and runs, answering --version, --help, and status commands, with 2186 vitest tests passing across 12 packages (agent, acn, acn-protocol, sdk, utils, version, storage, release, harness-connections, providers, client-common, cli) after fixing umask-induced git mode errors in the VCS backend and stale protocol import paths in utils patch tests;
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 93.3 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- git VCS tests fail: "invalid tree entry mode: '100664'" — container umask 0002 creates files with modes git rejects8 minutes
- utils patch tests fail: cannot find module '../../../../protocol/src/schemas/display' — protocol package renamed to acn-protocol3 minutes
- daemon-management: 28 tests fail — missing native binaries dist/native/linux-x64/desktop-host.node and magnitude-command
- Install time
- 25 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 3 hit, 2 fixed with no human help
- How the result was proved
- bun run cli/src/index.ts --version returned '0.2.0-alpha.1', bun run cli/src/index.ts status returned 'Runtime Stopped, Owner None', and vitest ran 2186 passed / 158 skipped / 28 failed (all failures from missing native binaries) across all workspace packages
- Model tokens used
- 332,103
- Exact commit tested
- b3e5a06bda3e
- 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.
Two issues were found, diagnosed, and fixed: - **`umask 0002` mode issue**: Container creates files with mode `100664` which just-git's tree ent… - **Stale import paths**: Utils patch tests referenced `../../../../protocol/src/` which no longer … One unfixable gap: `daemon-management` needs native binaries (`desktop-host.node`, `magnitude-comma… 2026-09-30T08:07:50.109505Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… tokens used 332,103 Here's the final result: Two issues were found, diagnosed, and fixed: - **`umask 0002` mode issue**: Container creates files with mode `100664` which just-git's tree ent… - **Stale import paths**: Utils patch tests referenced `../../../../protocol/src/` which no longer … One unfixable gap: `daemon-management` needs native binaries (`desktop-host.node`, `magnitude-comma…
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.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Took 25 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
- Hit 3 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 Rust projects Argusic has installed and timed, magnitude was the 6th fastest to reach a running state, and 8 of 8 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.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/magnitude)Questions
- Does magnitude run?
- Yes. magnitude runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test magnitude?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b3e5a06bda3e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test magnitude?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does magnitude 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 magnitude need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing magnitude?
- 3 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 magnitude compare with the alternatives?
- Of the 8 Rust projects Argusic has installed and timed, magnitude was the 6th fastest to reach a running state, and 8 of 8 reached one at all.
- Where is the evidence for magnitude?
- 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.