zigzag
Free, open-source embroidery software for Mac and Windows. Turn SVG artwork into machine embroidery, edit stitches visually, and create designs with AI agents via MCP.
Runssource: GitHubhomepageRustApache-2.0commit 429a02805414
Rust, Apache-2.0 licensed. The project labels itself: brother skitch, embroidery, embroidery digitizing, embroidery software, machine embroidery, macos, mcp and model context protocol.
zigzag runs. An Argusic agent installed it in 13 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
Rust 1.100.0 installed, project builds with default/gui/ble features; CLI zigzag converts SVG to PES/DST/EXP/JEF/VP3 embroidery files and traces PNGs; lib test suite (236 pass) and GUI test suite (265 pass) clean; studio GUI launches on Xvfb display; 2 pre-existing lettering test failures remain unfixed
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 80 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.
- lettering::editing_tests::text_is_sewn_the_same_wherever_its_moved: assertion failed - run 0: 184 stitches for 183 after moving text by (128.6, -44.1). Pre-existing bug in repo single commit.
- lettering::tests::text_is_selected_with_shift_arrows_double_clicks_drags_and_typed_over: unwrap() on None at lettering.rs:1739. Pre-existing bug in repo single commit.
- Install time
- 13 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 2 hit, 0 fixed with no human help
- How the result was proved
- cargo test (lib) exited 0, 233 lib + 3 mcp = 236 passed; cargo test --features gui exited 0, 265 passed, 2 pre-existing failures; zigzag convert examples/badge.svg -> PES (3203 st, 4 colors); -> DST; -> EXP (3190 st); -> JEF; -> VP3; -> SVG preview; -> HTML worksheet; zigzag convert examples/agent-badge-preview.png traced to PES (16317 st, 7 colors); zigzag info/fabrics/machines printed correct data; zigzag-studio --help printed usage; zigzag-studio launched on DISPLAY=:99 (Xvfb) stayed up 8s until timeout (exit 124); zigzag --version printed 0.1.5
- Model tokens used
- 47,682
- Exact commit tested
- 429a02805414
- 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.
**Verification:** - `cargo test` (lib + MCP bridge): **236 passed, 0 failed** - `cargo test --features gui` (studio + lettering): **265 passed, 2 failed** (both pre-existing let… - `zigzag convert badge.svg` produced valid PES, DST, EXP, JEF, VP3, SVG preview, and HTML workshee… - `zigzag convert agent-badge-preview.png` traced a photo to PES (16317 st, 7 colors) - `zigzag info`, `zigzag fabrics`, `zigzag machines` all printed correct data - `zigzag-studio --help` printed usage; launched on Xvfb `:99` and stayed up 8 seconds until timeou… - `zigzag --version` → 0.1.5 **2 pre-existing bugs found** (in `src/studio/lettering.rs`): 1. `text_is_sewn_the_same_wherever_its_moved` — stitch count mismatch (184 vs 183) after specific t… 2. `text_is_selected_with_shift_arrows_double_clicks_drags_and_typed_over` — unwrap on `None` in ty… These exist in the repo's single commit and are unaffected by anything in this environment.
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 13 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Hit 2 errors during setup, 2 of which were not solved.
- 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.
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)
brother-skitchembroideryembroidery-digitizingembroidery-softwaremachine-embroiderymacosmcpmodel-context-protocolrustsvgvector-editorwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zigzag)Questions
- Does zigzag run?
- Yes. zigzag runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test zigzag?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 429a02805414. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test zigzag?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does zigzag take to install?
- 13 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 zigzag need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing zigzag?
- 2 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
- Where is the evidence for zigzag?
- 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.