mozaik-network
The communication network for AI agents.
Runssource: GitHubhomepageTypeScriptMITcommit 32666f9c2b0b
TypeScript, MIT licensed. The project labels itself: agent collaboration, agent framework, agentic engineering, ai developer tools, ai infrastructure, concurrent agents, event driven agents and real time agents.
mozaik-network runs. An Argusic agent installed it in 0.1 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Mozaik Network server starts on port 3000, serves REST API endpoints (create/list networks, create peers, create/revoke invites) and WebSocket connections for peer messaging; all 47 automated tests pass covering HTTP endpoints, WebSocket messaging, peer join/leave/reconnect, invite-based access, metering, and the client SDK (rule engine, send limits, invite link parsing).
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 18.19.1 is too old for @rstest/core (requires >=20)2 minutes
- Install time
- under a minute
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test with Node 22: rstest run exited 0, all 47 tests passed (8 test files, 0 failures, 0 skipped); server started and returned HTTP 201 on POST /networks and POST /peers, HTTP 200 on GET /networks, HTTP 404 on unknown routes
- Model tokens used
- 89,382
- Exact commit tested
- 32666f9c2b0b
- 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.
socket.on("error", (error) => {
console.error(error)
})
})
return httpServer
}
Now I have all the information I need. Let me compile the final result.
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
succeeded in 0ms:
tokens used
89,382Replay 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 0.1 minutes.
- Recovered from all 1 error 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 0.1 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)
agent-collaborationagent-frameworkagentic-engineeringai-developer-toolsai-infrastructureconcurrent-agentsevent-driven-agentsreal-time-agentstypescript-aitypescript-framework
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mozaik-network)Questions
- Does mozaik-network run?
- Yes. mozaik-network runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test mozaik-network?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 32666f9c2b0b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mozaik-network?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mozaik-network take to install?
- 0.1 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 mozaik-network need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mozaik-network?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for mozaik-network?
- 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.