life-distributable

A personal agent that works on your life around the clock, on a Mac you own. One sentence to Claude Code installs it.

Runssource: GitHubhomepageGoMITcommit 2b222c753fba

Go, MIT licensed. The project labels itself: agent swarm, agentic ai, ai agents, ai assistants, ai enablement, ai swarm, claude code and golang.

life-distributable runs. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The hub Go backend and lifectl CLI compile and serve HTTP, all 27 Go packages pass fmt/vet/test (gofmt ok, vet ok, 0 test failures), the web console JS passes syntax check and unit tests, Python scripts pass lint, and the hub binary launches and responds on /healthz (200), /api/v1/status (200 authenticated), and / (200 authenticated).

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.12 (measured)
recorded runs
1
last tested
stars
413
forks
15
open issues
0
watchers
0
size
33 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 life-distributable, 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.

  • Go 1.26 compiler not installed on system3 minutes
  • Go std lib not in compiler tree (split package)1 minute
  • codesign not found (macOS-only tool)
Install time
8 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
go test -count=1 ./...: 27 packages, 0 failures across all; gofmt, go vet, 13 Python lint, 27 JS files + tests all pass; hub binary starts and serves HTTP - healthz 200, status 401 without auth then 200 with Bearer token, index 200
Model tokens used
130,602
Exact commit tested
2b222c753fba
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 1, 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.

- The `hub` binary starts on a TCP socket and correctly serves:
  - `/healthz` → 200
  - `/api/v1/status` → 401 without auth, 200 with Bearer token
  - `/` (web console) → 200 with auth
- **13 Python scripts** pass lint
- **27 JS files** + unit tests pass the webcheck suite
**Expected gaps (Linux, not macOS):**
- `codesign` is macOS-only — the build works before that step, the binaries are correct ELF files
- `swiftc` / mic helper not available — `make build` skips mic gracefully
- iOS Simulator / macOS Catalyst builds can't run — no Xcode
- Tailscale cert/key validation is skipped — config validation in `Load()` requires a `.ts.net` add…
The `hubverify` helper directory is still in `hub/cmd/` but doesn't affect tests.

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 8 minutes.
  • Recovered from all 3 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.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 8 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 Runner1/3Runs100.000.12

Topics (from GitHub)

agent-swarmagentic-aiai-agentsai-assistantsai-enablementai-swarmclaude-codegolangioslife-osllmmacosmulti-agentpersonal-agentpersonal-assistantproductivityself-hostedswiftuiworkflow-automation

Embed the badge

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

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

Questions

Does life-distributable run?
Yes. life-distributable runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test life-distributable?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2b222c753fba. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test life-distributable?
The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does life-distributable take to install?
8 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 life-distributable need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing life-distributable?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for life-distributable?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion