TidGi-Desktop
TidGi is an privacy-in-mind, automated, auto-git-backup, freely-deployed knowledge management Desktop note app, based on Tiddlywiki, with REST API for web-clipping and Anki connect. 「 太记 」是一个基于「 太微 TiddlyWiki 」的知识管理桌面应用,能保护隐私内容、高级自动化、自动Git云备份、部署为博客,且可通过RESTAPI与Anki等应用连接。(迭代开发中欢迎试用,开发进度见下方链接)(Under active development, see website below for details)
Runssource: GitHubhomepageTypeScriptMPL-2.0commit b4540b409b6d
TypeScript, MPL-2.0 licensed. The project labels itself: all in one, anki, backlinks, electron, evernote, knowledge graph, knowledge management and linux.
TidGi-Desktop runs. An Argusic agent installed it in 5 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
TidGi desktop app dependencies installed, 100 test suites pass (677 tests), TiddlyWiki plugins compile, and the Electron app launches and initializes workspaces successfully.
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.
- Node.js v18 pre-installed, needs ≥22.13 for pnpm1 minute
- corepack signature error preventing pnpm use1 minute
- pnpm lockfile missing @types/trusted-types entry1 minute
- Electron SUID sandbox helper not configured0.5 minutes
- cross-env not in PATH from .bin symlinks0.5 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npm exec pnpm install exited 0; vitest run via electron: 100 test files passed, 677 tests passed, 3 skipped; electron-forge start produced initialization logs; electron --version returned v43.2.0
- Model tokens used
- 51,503
- Exact commit tested
- b4540b409b6d
- 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.
I have all the data I need. Let me compile the final report. Here's the summary of all findings: **Install**: Worked after installing Node.js v22.23.5 and pnpm 11.17.0. Dependencies installed, git… **Tests**: 100 test files passed — 677 tests passed, 3 skipped. **App launch**: `electron-forge start` launched and produced initialization logs (workspace setup, … **Errors encountered**: 1. Node.js v18 pre-installed (needs ≥22.13 for pnpm 11.17). Fixed: downloaded v22.23.5 binary. 2. pnpm not found / corepack signature error. Fixed: installed pnpm via npm -g with writable prefix. 3. Lockfile missing `@types/trusted-types`. Fixed: `pnpm install --no-frozen-lockfile`. 4. Electron SUID sandbox helper error. Fixed: `ELECTRON_DISABLE_SANDBOX=1`. 5. `cross-env` not in PATH. Workaround: exported env vars directly. 6. `zx` module path mismatch. Workaround: used `node_modules/zx/build/cli.js`.
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 5 minutes.
- Recovered from all 5 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 MPL-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 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)
all-in-oneankibacklinkselectronevernoteknowledge-graphknowledge-managementlinuxlocal-firstmacosnote-takingnotebooknotes-appnotionobsidianpkmtiddlywikitiddlywiki5windowszettelkasten
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tidgi-desktop)Questions
- Does TidGi-Desktop run?
- Yes. TidGi-Desktop runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test TidGi-Desktop?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b4540b409b6d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test TidGi-Desktop?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does TidGi-Desktop take to install?
- 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 TidGi-Desktop need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing TidGi-Desktop?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for TidGi-Desktop?
- 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.