anydoc
Convert Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, and PDF to clean Markdown. Built in Rust, with Node.js and Python bindings.
Runssource: GitHubhomepageRustMITcommit 261fc257d17c
Rust, MIT licensed.
anydoc runs. An Argusic agent installed it in 16 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Rust crate anydoc v0.2.4 builds and passes all 296 tests; Python package firecrawl-anydoc builds via maturin, installs, and passes all 11 Python tests; the library converts docx, doc, ppt, pptx, odt, ods, xlsx, csv, epub, rtf, and PDF to correct GitHub-Flavored Markdown via both Rust and Python APIs; Node.js bindings require Node >= 20 (container has 18.19.1) and were not built.
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.
- Install time
- 16 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo test: 286 unit + 9 snapshot + 1 robustness = 296 passed; python3 test_anydoc.py: 11 passed; cargo run --example convert on docx/doc/ppt/pptx/xlsx/ods/odt/csv/rtf/epub all produced correct Markdown; python3 anydoc.to_markdown() on all 10+ formats succeeded
- Model tokens used
- 143,505
- Exact commit tested
- 261fc257d17c
- 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.
OK tests/fixtures/odp/pres.odp: 272 chars OK tests/fixtures/doc/text.doc: 1225 chars The repo is fully operational. Here's the final report: **Build & Install**: Cargo build succeeded. `cargo test` passed: **296 tests** (286 unit + 9 snapsh… **Library exercise**: The Rust example (`cargo run --example convert`) successfully converted docx,… **No errors encountered during the process.** tokens used 143,505 The repo is fully operational. Here's the final report: **Build & Install**: Cargo build succeeded. `cargo test` passed: **296 tests** (286 unit + 9 snapsh… **Library exercise**: The Rust example (`cargo run --example convert`) successfully converted docx,… **No errors encountered during the process.**
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 16 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- Following its own README: the documented path worked with nothing to fix.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/anydoc)Questions
- Does anydoc run?
- Yes. anydoc runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test anydoc?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 261fc257d17c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test anydoc?
- 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 anydoc take to install?
- 16 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 anydoc need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing anydoc?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for anydoc?
- 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.