Vibeleaderboard
Index / tool

Weft Coordination Protocol

github.com/celador/weft
Visit github.com
Category
AI Agents
Rank
No. 3739Tools index

Previous survey · No. 3562 ·

Pricing
Open Source
Type
TOOL
Use case
Agent Building · Coding
Interfaces
API
GitHub
45 stars
Latest release
vscode-v0.1.1
Date

About

Weft coordinates parallel coding agents while they edit, not only when they open a pull request. Agents submit tool-call edits to a per-repository sequencer, which validates each edit against changes accepted since the agent's base and returns diagnostics to the agent. It is built on Cloudflare and works across agent harnesses.

At a glance

Weft coordinates concurrent coding agents by checking their edits against an ordered record of accepted changes. It is worth exploring if agents frequently work from stale versions of the same repository.

Good fit

Teams researching coordination at edit time instead of finding every conflict at pull request review.

Consider something else when

Use separate worktrees and ordinary review if agents rarely touch overlapping code or you need a mature deployment.

Start here

Read a sample event sequence and follow an edit based on old state. Check what feedback the agent receives and what a human can pause or inspect.

Cost and requirements

MIT-licensed research implementation with harness adapters and a Cloudflare-backed coordinator. A deployment has separate infrastructure and agent requirements.

Limits to know

The project calls the wire protocol a draft. The coordinator can only reason from the edits and state it receives. Review what code and evidence would be sent before connecting a private repository.

Tags

coding-agentcoordinationprotocolcloudflaremulti-agentmit

Tech Stack

Node.js

Comments (0)

No comments yet

Editorially curated, with community endorsements as a secondary signal. Corrections welcome.