FridayOS1.0
Local-first AI second brain & personal knowledge management: Six-Brain Markdown blueprint, Obsidian example vault, offline deployment and bilingual guides. 六脑方法 · 本地知识管理
Runssource: GitHubhomepagePythonMITcommit eaf305360eb3
Python, MIT licensed. The project labels itself: ai, ai agents, fridayos, human ai collaboration, knowledge management, local first, markdown and obsidian.
FridayOS1.0 runs. An Argusic agent installed it in 30 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All three repo-local Python scripts run successfully: the demo brain generator produces 129 wiki files matching the shipped zip content, the transcript parser converts 188 JSONL files to 179 markdown docs, and the star history script works offline. The demo zip (182 entries) passes CRC integrity checks and all media files decode.
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 96 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.
- FridayOS-Lite示例大脑生成器.py had hardcoded absolute BASE path '/sessions/friendly-upbeat-wozniak/...' causing PermissionError5 minutes
- docs/images/gif/node.gif has LZW decode error in one frame (202/210 frames decode)2 minutes
- Install time
- 30 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- python3 FridayOS-Lite示例大脑生成器.py returned 'v2 完成。员工: 100' and generated 129 markdown files matching the shipped zip; python3 parse_transcripts.py (in FridayOS-Lite实测/) generated 179 markdown files from 188 JSONL transcripts; python3 update_star_history.py --count 901 produced valid CSV+SVG; unzip testzip passed for 示例大脑-云栈科技.zip; ffmpeg decode passed for all 12 gifs and 3 pngs (1 GIF had minor LZW warning)
- Model tokens used
- 171,913
- Exact commit tested
- eaf305360eb3
- 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.
- The generator script produces 129 wiki markdown files + 1 CSV, matching all 129 common files in t…
- The parser converts 188 JSONL files to 179 readable markdown transcripts
- The star history script appends a date to the snapshot CSV and regenerates the SVG (valid)
- The zip is valid with 182 entries
- All media decodes (1 minor LZW warning in `node.gif`)
Now I need to construct the single-line JSON result. Let me be very careful about the format:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 30, "errors": [{"msg": "..…
For `verified_how`, I need the exact command and what it returned. The most meaningful verification…
- `python3 FridayOS-Lite示例大脑生成器.py` → "v2 完成。员工: 100"
- `python3 parse_transcripts.py` → "✅ transcripts-md/..." 179 files
- `python3 update_star_history.py --count 901` → generated CSV+SVG
Let me write the final result now.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.
- Recovered from all 2 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 30 minutes to install, slower than the median of the 40 comparable projects Argusic has measured.
Of the 41 agents projects Argusic has installed and timed, FridayOS1.0 was the 38th fastest to reach a running state, and 29 of 41 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.
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 | Runs with mocks | 92.00 | 0.02 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.10 |
Topics (from GitHub)
aiai-agentsfridayoshuman-ai-collaborationknowledge-managementlocal-firstmarkdownobsidianobsidian-vaultpersonal-knowledge-managementsecond-brain
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/fridayos1-0)Questions
- Does FridayOS1.0 run?
- Yes. FridayOS1.0 runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test FridayOS1.0?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit eaf305360eb3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test FridayOS1.0?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does FridayOS1.0 take to install?
- 30 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 FridayOS1.0 need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing FridayOS1.0?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does FridayOS1.0 compare with the alternatives?
- Of the 41 agents projects Argusic has installed and timed, FridayOS1.0 was the 38th fastest to reach a running state, and 29 of 41 reached one at all.
- Where is the evidence for FridayOS1.0?
- 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.