Turn your goal into a clear task graph
Before any agent edits a file, Meshloop breaks your goal into bounded tasks with explicit file ownership and verification checks. You review and approve the plan—or adjust it—before execution starts.
How Meshloop works
Four stages from intent to a clean merge.
Meshloop separates planning, parallel building, independent verification, and human acceptance so no agent can silently rewrite its own scope or merge unverified code.
Every task runs in its own Git sandbox
Independent tasks run concurrently in separate Git worktrees. Each agent receives only the structural context it needs for its assigned files, keeping runs fast and conflict-free.
Real checks decide, and bad fixes roll back
After an agent edits code, Meshloop runs your compiler, linter, and tests. If a check fails, the agent gets a bounded chance to fix the error—and if its fix increases error counts, Meshloop reverts the attempt immediately.
You decide what lands on your branch
A fresh reviewer checks the verified diff against your original specification. Only when you explicitly accept the result does Meshloop merge the changes into your working branch.
Clear boundaries
What Meshloop handles—and what stays yours.
Meshloop is a local execution runtime, not a hosted platform or a replacement for engineering judgment.
| Area | What Meshloop guarantees | What stays outside Meshloop |
|---|---|---|
| Branch safety | All agent edits happen in disposable Git worktrees until you run the accept gate. | Automatic pushes to remote branches or unauthorized pull requests. |
| Verification | Real exit codes from your compiler, linter, and test suite gate every task transition. | Replacing your product architecture or domain-specific acceptance criteria. |
| Cost & runaway protection | Hard limits on repair attempts, wall-clock timeouts, and automatic rollback when errors grow. | Billing you for tokens—Meshloop uses your existing CLI logins and API keys. |
| Runtime footprint | One local Rust binary with local state—no background daemon or cloud account required. | Hosted multi-tenant SaaS dashboards (pair with Dendro for fleet analytics). |