writer-framework
No-code in the front, Python in the back. An open-source framework for creating data apps.
Runssource: GitHubhomepagePythonApache-2.0commit 53eef36becc2
Python, Apache-2.0 licensed. The project labels itself: ai, ai in, data apps, data visualization, developer tools, interface, interface builder and models.
writer-framework runs. An Argusic agent installed it in 3.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
writer CLI version 1.27.0 installed, Python package built, frontend static assets compiled, all 396 backend tests pass, and the hello app serves HTTP 200 on the designated port
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.
- npm build OOM on first attempt due to Node.js 18 vs required 221.5 minutes
- ModuleNotFoundError: No module named 'writer.ui' – ui.py was missing (needs frontend codegen)1 minute
- pytest not found initially – build group dependencies not installed0.5 minutes
- Install time
- 4 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest exited 0, 396 passed; curl http://127.0.0.1:5002 returned 200
- Model tokens used
- 163,276
- Exact commit tested
- 53eef36becc2
- 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.
WRITER FRAMEWORK v1.27.0 App is available at: http://127.0.0.1:5002 200 Everything works. Let me compile the final result. exec /bin/sh -lc 'export PATH="$HOME/.local/bin:$PATH" && cd /work/repo && which .venv/bin/writer && .ve… succeeded in 382ms: .venv/bin/writer WARNING - kv_storage - Missing required environment variables for KV storage access writer, version 1.27.0 tokens used 163,276
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 3.5 minutes, faster than the median of the 106 comparable projects Argusic has measured.
- 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.
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 107 ai projects Argusic has installed and timed, writer-framework was the 43rd fastest to reach a running state, and 73 of 107 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 3.5 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)
aiai-indata-appsdata-visualizationdeveloper-toolsinterfaceinterface-buildermodelsno-codepythonuiui-componentswebsockets
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/writer-framework)Questions
- Does writer-framework run?
- Yes. writer-framework runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test writer-framework?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 53eef36becc2. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test writer-framework?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does writer-framework take to install?
- 3.5 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 writer-framework need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing writer-framework?
- 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.
- How does writer-framework compare with the alternatives?
- Of the 107 ai projects Argusic has installed and timed, writer-framework was the 43rd fastest to reach a running state, and 73 of 107 reached one at all.
- Where is the evidence for writer-framework?
- 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.