tinylittleoffice
A free office suite where your document is inside the link and easy to share. There's no account and nothing saved unless you choose.
Could not verifysource: GitHubhomepageTypeScriptMITcommit c61ca63589b1
TypeScript, MIT licensed. The project labels itself: cloudflare workers, lit, local first, no backend, office suite, privacy, pwa and web components.
Argusic could not get tinylittleoffice running. An Argusic agent hit no errors on a clean machine with no GPU, and the whole session was recorded.
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 20 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.
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- Model tokens used
- 144,815
- Exact commit tested
- c61ca63589b1
- 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.
- Install time
- the run did not report one
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Note: We need to obey AGENTS.md. Let me check. Let me start. I'll run pwd, ls, and git status. Also check for AGENTS.md files maybe in the repo. U… After exploring, I'll likely need to understand the task. The user hasn't provided any prompt text … The developer message includes a summary of the current task? Let me re-read. It says "Here are the… But maybe there is an implicit user query? The prompt includes "Within this context, Argusic Agent … I need to be careful: the instructions say "Please keep going until the query is completely resolve… Let me craft a short, friendly response asking what they'd like help with, noting I can inspect the… </p> Let's write a warm, concise message. Final response: "Hi! What would you like me to work on? I can explore the current workspace, debug issues, implemen… That's about right. No tool calls yet because no task.
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
- Nothing broke on the way: zero errors between clone and running.
- 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
- An agent with no time limit did not get it running.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 20.00 | 0.28 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.26 |
Topics (from GitHub)
cloudflare-workerslitlocal-firstno-backendoffice-suiteprivacypwaweb-components
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tinylittleoffice)Questions
- Does tinylittleoffice run?
- Argusic could not verify that tinylittleoffice runs. Argusic installed and launched it on a clean machine, hitting 0 errors on the way, and recorded the session.
- How did Argusic test tinylittleoffice?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c61ca63589b1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test tinylittleoffice?
- The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- Does tinylittleoffice need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tinylittleoffice?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for tinylittleoffice?
- 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.