takumi
Render OG images and paged PDFs from JSX, HTML, and CSS. No headless browser. Runs on Node.js, Cloudflare Workers, browsers, and Rust.
Runssource: GitHubhomepageRustApache-2.0commit 3141f1e5f14a
Rust, Apache-2.0 licensed. The project labels itself: cloudflare workers, gif, html to image, html to pdf, image generation, invoice, jsx and og image.
takumi runs. An Argusic agent installed it in 39 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Takumi monorepo builds and all test suites pass: 28 JS tests (takumi-js), 65 JS tests (takumi-napi native bindings), 122 Rust tests (takumi umbrella crate), 165 Rust tests (takumi-pdf), plus e2e rendering produces valid 1200x630 WebP images and valid PDF-1.7 documents from JSX templates
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.
- oxfmt test validation failed because oxfmt's CLI script uses regex flag /gv (requires Node 20+)5 minutes
- Node.js v18.19.1 too old for tsdown/rolldown (styleText in node:util)3 minutes
- Node.js v18.19.1 is too old for napi-rs CLI (@inquirer/core uses styleText from node:util)2 minutes
- Install time
- 39 minutes
- Cold machine to finish
- 43 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- bun run --bun --filter takumi-js test: 28 pass, 0 fail; cd takumi-napi && bun test: 65 pass, 0 fail; cargo test -p takumi: 122 passed (16 cascade + 10 fixture + 7 font + 1 html_fixture + 57 measure + 2 memory + 4 oversized + 14 pseudo + 1 svg_parity + 5 svg_render + 4 svg_text + 1 doc_test); cargo test -p takumi-pdf: 66 unit + 99 fixture tests passed; e2e: render(JSX->1200x630 WebP, validated via ffprobe) + render(JSX->PDF-1.7, validated via header/EOF)
- Model tokens used
- 512,004
- Exact commit tested
- 3141f1e5f14a
- 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.
test result: ok. 14 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.15s test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 23.98s test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.59s Everything passes. Here's the final report: 2026-09-08T21:44:59.943866Z ERROR codex_core::session: failed to record rollout items: thread 01a08… 2026-09-08T21:44:59.943921Z ERROR codex_core::session: failed to record rollout items: thread 01a08… tokens used 512,004 Everything passes. Here's the 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.
- Installed in 39 minutes.
- Recovered from all 3 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 Apache-2.0, as reported by its host.
- Measured 4 times, so the result is not a one-off.
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
Topics (from GitHub)
cloudflare-workersgifhtml-to-imagehtml-to-pdfimage-generationinvoicejsxog-imageopengraphopengraph-imagespdfpdf-generationpdf-generatorpuppeteer-alternativerustsatorisocial-cardssvgwasm
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/takumi)Questions
- Does takumi run?
- Yes. takumi runs. Argusic installed and launched it on a clean machine in 39 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test takumi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3141f1e5f14a. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test takumi?
- The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does takumi take to install?
- 39 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 takumi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing takumi?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for takumi?
- All 4 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.