doxx

Expose the contents of .docx files without leaving your terminal. Fast, safe, and smart, no Office required!

Runssource: GitHubhomepageRustMITcommit 062819a10f42

Rust, MIT licensed. The project labels itself: cli, docx, msword, render, rust, terminal and tui.

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

doxx builds, all 235 tests pass (including 6 ANSI export tests), binary reports version 0.1.4, text and ANSI exports work on fixture .docx files, clippy reports zero warnings.

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.10 (measured)
recorded runs
2
last tested
stars
3,791
forks
99
open issues
14
watchers
9
size
100 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 doxx, 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.

  • ANSI color export tests failed because crossterm 0.28's Display impl for SetForegroundColor produces only \x1b[m instead of \x1b[38;5;Nm or \x1b[38;2;R;G;Bm, causing test_ansi_export_color_depths and test_ansi_export_formatting to fail15 minutes
Install time
7 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
cargo test --all-features: 235 passed, 0 failed across 12 test suites; cargo run -- --version returned 'doxx 0.1.4'; cargo run -- tests/fixtures/minimal.docx --export text printed correct document text; cargo run -- tests/fixtures/comprehensive.docx --export ansi emitted proper ANSI escape sequences
Model tokens used
63,001
Exact commit tested
062819a10f42
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.

Start time: 1794188723
1794189018
The timestamp of the repo file might not reflect when I started. Let me estimate — the process took…
Here's my final report:
```
```
tokens used
63,001
The timestamp of the repo file might not reflect when I started. Let me estimate — the process took…
Here's my final 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.
  • 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.

What did not, or is not known

  • Took 7 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.

Of the 124 cli projects Argusic has installed and timed, doxx was the 93rd fastest to reach a running state, and 112 of 124 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 7 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.10
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

clidocxmswordrenderrustterminaltui

Embed the badge

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

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

Questions

Does doxx run?
Yes. doxx runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test doxx?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 062819a10f42. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test doxx?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does doxx take to install?
7 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 doxx need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing doxx?
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 doxx compare with the alternatives?
Of the 124 cli projects Argusic has installed and timed, doxx was the 93rd fastest to reach a running state, and 112 of 124 reached one at all.
Where is the evidence for doxx?
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