obsidian-wiki

Framework for AI agents to build and maintain a digital brain through Obsidian wiki | Memory System for Agents

Runssource: GitHubPythonMITcommit 2f1014299134

Python, MIT licensed. The project labels itself: agent memory, agent skills, brain, claude code, claude skills, codex, karpathy and knowledge base.

obsidian-wiki runs. An Argusic agent installed it in 3.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

obsidian-wiki package installs from source in a venv, setup writes config and provisions skills into 12 agent directories, 1029/1032 tests pass, doctor reports all-clear, the FastAPI/MCP server starts on demand and serves health, search, pages, memory, context-pack, staging, and status endpoints over HTTP.

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

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
2
last tested
stars
3,755
forks
376
open issues
10
watchers
16
size
12 MB
created
last push

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.

Time lost to each failure while testing obsidian-wiki, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • pip install failed: externally-managed-environment (PEP 668)0.5 minutes
  • test_sync.py failed: git commit returned 128 (no user.email/user.name)0.1 minutes
Install time
4 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
pytest tests/ -q: 1029 passed, 3 skipped, 29 subtests passed; obsidian-wiki doctor: pass; curl localhost:19543/health returned 200; Memory API roundtrip (remember/search/recap) confirmed
Model tokens used
41,071
Exact commit tested
2f1014299134
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.

exec
/bin/sh -lc 'cd /work/repo && /tmp/venv/bin/python -m pytest tests/ -q --tb=no 2>&1 | tail -5' in /…
 succeeded in 77139ms:
.................................................................. [ 80%]
........................................................................ [ 87%]
........................................................................ [ 94%]
.....................................................                    [100%]
1029 passed, 3 skipped, 29 subtests passed in 76.44s (0:01:16)
All 1029 tests pass (3 skipped as expected), the CLI installs and configures vaults, the doctor che…
tokens used
41,071
All 1029 tests pass (3 skipped as expected), the CLI installs and configures vaults, the doctor che…

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 3.5 minutes to install, slower than the median of the 122 comparable projects Argusic has measured.

Of the 123 agent-skills projects Argusic has installed and timed, obsidian-wiki was the 77th fastest to reach a running state, and 94 of 123 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.07
Argusic Runner1/3Runs with mocks92.000.02

Topics (from GitHub)

agent-memoryagent-skillsbrainclaude-codeclaude-skillscodexkarpathyknowledge-baseknowledge-graphllm-toolsllm-wikimcpmemoryobsidianobsidian-brainpkmsecond-brainwiki

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/obsidian-wiki.svg)](https://argusic.com/subject/obsidian-wiki)

Questions

Does obsidian-wiki run?
Yes. obsidian-wiki runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test obsidian-wiki?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2f1014299134. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test obsidian-wiki?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does obsidian-wiki 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 obsidian-wiki need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing obsidian-wiki?
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 obsidian-wiki compare with the alternatives?
Of the 123 agent-skills projects Argusic has installed and timed, obsidian-wiki was the 77th fastest to reach a running state, and 94 of 123 reached one at all.
Where is the evidence for obsidian-wiki?
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.

Discussion