mulmoclaude

Nurture your own AI assistant on your own computer. Local-first and MIT: memories, data and apps stay as plain files in your workspace. Chat summons the right GUI, wiki, spreadsheet, chart, form, 3D. Build small apps for an audience of one, no programming required.

Runssource: GitHubhomepageTypeScriptMITcommit d7dadff432a4

TypeScript, MIT licensed. The project labels itself: ai agents, ai assistant, ai native, chat ui, claude, claude code, knowledge management and local first.

mulmoclaude runs. An Argusic agent installed it in 9 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Dependencies install, workspace packages build, plugin codegen, 11180 unit tests pass, and the Express API server starts on port 3001 and responds to authenticated API requests.

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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.18 (measured)
recorded runs
2
last tested
stars
390
forks
64
open issues
18
watchers
3
size
56 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 mulmoclaude, 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.

  • Node.js v18.19.1 is too old (project requires >=22.19)2 minutes
  • Workspace package dist/ missing (ERR_MODULE_NOT_FOUND @mulmoclaude/accounting-plugin)2 minutes
  • Server crashed: ~/.claude/ not found (assertClaudeFiles exits process)2 minutes
  • yarn not found on system PATH1 minute
Install time
9 minutes
Cold machine to finish
9 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
yarn test exited 0: 11180 passed, 0 failed, 14 skipped. Server started on :3001, GET /api/sessions with Bearer token returned HTTP 200 with session list.
Model tokens used
253,281
Exact commit tested
d7dadff432a4
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.

2. **yarn not found** — system package manager lacked yarn. Used corepack (bundled with Node.js 22)…
3. **`yarn install`** — completed in 41s with peer-dependency warnings only (non-fatal).
4. **`yarn build:packages`** — initially failed because `@mulmoclaude/accounting-plugin/dist/shared…
5. **`yarn plugins:codegen`** — succeeded, discovered 17 metas.
**Test verification:**
- `yarn test` ran the full node:test suite: **11180 passed, 0 failed, 14 skipped** across 2399 suit…
**Server verification:**
- The server crashed on startup because `isDockerAvailable()` calls `assertClaudeFiles()` which che…
- **Fix**: Set `DISABLE_SANDBOX=1` to bypass the sandbox/claude check.
- Server started on port 3001, logging: `[server] listening port=3001`.
- `curl -H "Authorization: Bearer $(cat ~/mulmoclaude/.session-token)" http://localhost:3001/api/se…
- Docker and Gemini warnings are expected (no docker daemon, no API key in this container).

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

Of the 124 ai-agents projects Argusic has installed and timed, mulmoclaude was the 84th fastest to reach a running state, and 96 of 124 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 9 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.18
Argusic Runner1/3Did not run20.000.21

Topics (from GitHub)

ai-agentsai-assistantai-nativechat-uiclaudeclaude-codeknowledge-managementlocal-firstmcpno-codepersonal-assistantpersonal-wikipluginsprivacyschema-drivenself-hostedtypescript

Embed the badge

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

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

Questions

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