presenterm
A markdown terminal slideshow tool
Runssource: GitHubhomepageRustBSD-2-Clausecommit 5f8add11a24a
Rust, BSD-2-Clause licensed. The project labels itself: cli, markdown, markdown slides, presentation, rust, slides, slideshow and terminal.
presenterm runs. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
presenterm 0.16.1 builds, all 520 unit tests pass, non-interactive commands (--help, --version, --current-theme, --list-comment-commands, --acknowledgements, --export-html) function correctly; HTML export of demo presentation produces valid 324KB output.
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.
- Interactive TUI commands (--list-themes, --validate-overflows, present) fail in headless environment with 'No such device or address (os error 6)' from kitty image protocol requiring a real TTY5 minutes
- PDF export requires weasyprint (Python library) which is not installed in container
- Install time
- 1 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test exited 0 (520 passed, 0 failed); ./target/debug/presenterm --version returned 'presenterm 0.16.1'; --current-theme returned 'dark'; --list-comment-commands returned 23 commands; --export-html produced 323746-byte valid HTML; --help shows full CLI usage
- Model tokens used
- 51,734
- Exact commit tested
- 5f8add11a24a
- 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.
<!-- speaker_note: Your note here --> <!-- snippet_output: identifier --> <!-- comment: hi mom --> EXIT: 0 Good, it works fine standalone. The earlier abort was from the for-loop piping. Everything is verif… Here is the final summary: 2026-10-02T07:37:40.204731Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-10-02T07:37:40.204771Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… tokens used 51,734 Good, it works fine standalone. The earlier abort was from the for-loop piping. Everything is verif… Here is the final summary:
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 1 minute, faster than the median of the 37 comparable projects Argusic has measured.
- 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 BSD-2-Clause, 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.
Of the 38 cli projects Argusic has installed and timed, presenterm was the 6th fastest to reach a running state, and 34 of 38 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 1 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
Topics (from GitHub)
climarkdownmarkdown-slidespresentationrustslidesslideshowterminal
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/presenterm)Questions
- Does presenterm run?
- Yes. presenterm runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test presenterm?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5f8add11a24a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test presenterm?
- 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 presenterm take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does presenterm need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing presenterm?
- 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 presenterm compare with the alternatives?
- Of the 38 cli projects Argusic has installed and timed, presenterm was the 6th fastest to reach a running state, and 34 of 38 reached one at all.
- Where is the evidence for presenterm?
- 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.