obsidian-mind

A self-organizing Obsidian vault that gives AI coding agents persistent memory.

Runssource: GitHubTypeScriptMITcommit af615d100a1d

TypeScript, MIT licensed. The project labels itself: ai agents, claude code, codex cli, gemini cli, knowledge management, obsidian, obsidian vault and persistent memory.

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

488 unit tests pass, QMD semantic search indexes 28 markdown files and returns ranked results, SessionStart hook runs cleanly without assertion errors or subprocess timeouts

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.80 (measured)
recorded runs
2
last tested
stars
5,538
forks
616
open issues
16
watchers
16
size
7 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-mind, 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.

  • npm root -g subprocess took 3+ seconds to fail, causing integration test timeouts in subprocess-based hook tests30 minutes
  • @tobilu/qmd v2.8.3 exports-only package.json causes require.resolve() to fail for ./dist/cli/qmd.js subpath and for the package root (no exports main)10 minutes
Install time
45 minutes
Cold machine to finish
71 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
node --experimental-strip-types --test across 40+ test files reported 488 pass, 0 fail; qmd --index repo search 'North Star' returned ranked results with context strings; qmd bootstrap completed 21 files indexed
Model tokens used
465,941
Exact commit tested
af615d100a1d
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.

- Patched `resolveQmdEntry` in both `lib/qmd.ts` and `qmd-mcp.mjs` to use fast filesystem probes in…
- Re-ran QMD bootstrap (~21 vault files indexed) and confirmed `qmd search` returns results
### Verified
- 488 unit tests pass (`node --experimental-strip-types --test` across 40+ test files)
- `qmd --index repo search "North Star"` returns results with scores ~79%
- `qmd --index repo status` shows 28 files indexed, collection healthy
- SessionStart hook runs without assertion errors
### Changes made
| File | Change |
|------|--------|
| `.claude/scripts/lib/qmd.ts` | Replaced `npm root -g` subprocess with filesystem probes walking c…
| `.claude/scripts/qmd-mcp.mjs` | Same fix applied to the duplicated implementation |

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

Of the 122 ai-agents projects Argusic has installed and timed, obsidian-mind was the 113th fastest to reach a running state, and 94 of 122 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.80
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

ai-agentsclaude-codecodex-cligemini-cliknowledge-managementobsidianobsidian-vaultpersistent-memorysecond-braintemplate

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-mind.svg)](https://argusic.com/subject/obsidian-mind)

Questions

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