About
A workstation cleaner that understands what you are working on.
Task Manager shows six node.exe lines. A coding day is a tree of agents, MCP servers, terminals, dev servers and build output. SweepLoom exists to reclaim space from that tree without cutting the branch you are sitting on.
Who builds it
Sergii Ziborov, for Weavatrix.
SweepLoom is designed and written by Sergii Ziborov and published by Weavatrix. It is developed in the open at github.com/Weavatrix/sweeploom.
Weavatrix is the company; SweepLoom is the product. Weavatrix builds open infrastructure for AI software agents: repository evidence graphs, durable memory and safe action surfaces. SweepLoom applies the same habits, evidence first and explicit gates before any write, to the workstation itself.
SweepLoom builds on MIT-licensed libraries, weavatrix-scan, weavatrix-git and mcport (the MCP server layer), which remain MIT. SweepLoom itself is MPL-2.0.
It ships as a CLI, an MCP server with a Codex plugin, a Rust library and a nine-tab desktop app, all from one engine and one repository.
Principles
What SweepLoom will not trade away.
Local-first
Everything runs on your machine. No account, no cloud, no telemetry. The CLI path carries no HTTP client at all. The website you are reading has no analytics either: static files on nginx at Hetzner in Germany, access logging off, DNS by Cloudflare.
Gated apply
Nothing is deleted without plan, revalidate, execute and receipt. People consent with --apply or a confirmation; agents need confirm=true and explicit ids.
Keep live work
A live agent session is the most valuable thing on the machine, not the biggest. SweepLoom never offers to kill it from the CLI or MCP.
Deterministic where it matters
No LLM on classify or apply. The path that can remove files is plain, tested Rust that behaves the same every time.
Honest numbers
Benchmarks are tests that fail, not slides. When a live run found no token saving, that result was published next to the fixtures.
Open source
SweepLoom is MPL-2.0. You can read, build and change every line that touches your disk.
The name
A sweep that knows the weave.
A workstation is woven: an agent holds an MCP server, which holds a terminal, which started a dev server, which built into a folder in a project you are still editing. Sweeping blindly pulls threads. SweepLoom's mark is a loom's warp and weft inside a ring, and the job is to clear what is loose without unravelling what is in use.
Want to help? Read the docs, try it on your own machine, and open an issue when it gets something wrong.