durdraw
Versatile ASCII and ANSI Art text editor for drawing in the Linux/Unix/macOS terminal, with animation, 256 and 16 colors, Unicode and CP437, and customizable themes
Runssource: GitHubhomepagePythonBSD-3-Clausecommit bacad9c4c325
Python, BSD-3-Clause licensed. The project labels itself: animation, ansi, ansi art, ascii, ascii art, bbs, drawing and editor.
durdraw runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Durdraw 0.30.1 is installed in a Python venv, all 9 unit tests pass, and the curses-based ANSI/ASCII art editor launches, plays .dur files, and exits cleanly under a PTY.
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
- 2 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pytest test/ => 9 passed; durdraw -V => 0.30.1; script -qc durdraw --play file.dur --delayexit 0.5 => exit 0; script -qc durview file.dur => exit 0; script -qc echo q | durdraw => exit 0
- Model tokens used
- 55,612
- Exact commit tested
- bacad9c4c325
- 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.
No errors requiring patches were hit. The only "missing" thing is `durfetch` requires fastfetch/neo…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 2, "errors": [], "test_dep…
2026-10-05T16:19:31.182815Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-05T16:19:31.182855Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-05T16:19:31.182870Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-05T16:19:31.182888Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-05T16:19:31.182898Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
tokens used
55,612Replay 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 2 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 BSD-3-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.
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 2 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
Topics (from GitHub)
animationansiansi-artasciiascii-artbbsdrawingeditorlinuxncursesterminalterminal-arttext-editortextmodetuiunicodeunicode-artxterm-256color
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/durdraw)Questions
- Does durdraw run?
- Yes. durdraw runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test durdraw?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bacad9c4c325. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test durdraw?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does durdraw take to install?
- 2 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 durdraw need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing durdraw?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for durdraw?
- 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.