franz
Franz is a free messaging app for services like WhatsApp, Slack, Messenger and many more.
Runssource: GitHubhomepageJavaScriptApache-2.0commit 94b1ef298aa7
JavaScript, Apache-2.0 licensed. The project labels itself: electron, franz, messaging, messenger, office, productivity, slack and telegram.
franz runs. An Argusic agent installed it in 1.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.
npm install completes, all 4 TypeScript sub-packages compile, gulp build populates the build directory, electron-rebuild finishes, jest runs 6/6 passed, and the Electron app launches and stays up.
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.
- npx lerna bootstrap failed - lerna@10 incompatible with Node 182 minutes
- gulp build minify task never completed (terser async issue)
- gulp dev webserver failed - fs.watch recursive not available on platform
- Install time
- 2 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npx jest exited 0, 1 suite 6 passed; npx electron ./build --no-sandbox launched and stayed running for 8s without application errors
- Model tokens used
- 53,005
- Exact commit tested
- 94b1ef298aa7
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Here's the complete summary of what was done and what was observed. **Install**: `npm install` installed 2847 packages (36s). Sub-packages (`theme`, `forms`, `ui`, `ty… **Build**: `npx gulp build` populated `/work/repo/build/` with compiled output (typescript, html, s… **Errors encountered**: - `npx lerna bootstrap` failed because lerna@10 requires Node 22+, but the repo bundles [email protected]… - `gulp build` minify task hung indefinitely (gulp-terser async completion bug). The build output w… - `gulp dev` webserver task failed due to `fs.watch` recursive mode not being available on this pla… **Verification**: - `npx jest` → 1 test suite, 6 tests passed - `npx electron ./build --no-sandbox` → Electron started and remained running; the only output was … - `npm run rebuild` → Rebuild Complete **Tests**: Only one test file exists in the project (`src/features/utils/FeatureStore.test.js`), an…
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.5 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 2 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.
- A quick evaluation: it was running 1.5 minutes after the clone.
Run history
Topics (from GitHub)
electronfranzmessagingmessengerofficeproductivityslacktelegramwhatsapp
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/franz)Questions
- Does franz run?
- Yes. franz runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test franz?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 94b1ef298aa7. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test franz?
- 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 franz take to install?
- 1.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 franz need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing franz?
- 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 franz?
- 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.