Weft

Weft Coordination Protocol (WCP)

The Weft Coordination Protocol (WCP) offers a sophisticated solution for coordinating coding agents during their editing processes—moving beyond the conventional pull request initiation step. By allowing agents to submit tool-call edits to a dedicated sequencer for each repository, WCP validates edits against accepted changes made since the agent's base and returns actionable diagnostics through native hooks. This ensures that human operators can monitor the same event streams, with the ability to approve, pause, message, undo, or inspect any action taken.

Key Features

• Concurrent Workflows: WCP facilitates safer concurrent editing without file locks, enabling agents to operate independently without waiting for human intervention for merges.
• Harness-Neutral Protocol: WCP serves as a universal wire protocol for coordination, while Weft is its implementation hosted on Cloudflare, complete with a suite of necessary adapters.

Live Demo

Experience WCP in action at the public live demo: weft.elier.ai. This demo utilizes real event logs from the dogfood repository with a read-only interface, requiring no login.

Implementation Status

This project is currently in the research and demonstration phase. WCP v0.1 is a draft and has not yet been designated as a published standard. Further insights can be found in the design documentation, a detailed protocol specification, and guidance on how to experiment with it yourself.

Architecture Overview

The architecture of Weft can be visualized as follows:

flowchart LR
  subgraph agents[Agent workspaces]
    H[Claude Code / Codex / OpenCode / Hermes] --> A[Harness adapter + analyzer]
  end
  A -->|check / edit / events| G[Gateway]
  G --> C[Repo coordinator
Durable Object + SQLite
ordered WCP log]
  C -->|verdicts / diagnostics / inbox| A
  C --> Q[Queues]
  Q --> W[Workflows
process / select / land / revert]
  W --> S[Sandbox containers
merge / tests / agent]
  W --> R[Artifacts + evidence]
  G --> D[D1 index]
  HN[Human web / iOS clients] <-->|observe / human actions| G

• Adapters: Translate harness-specific hooks into WCP requests, ensuring compatibility with any coding agent and preventing protocol reliance on a single implementation.
• Durable Object: Assigns event orders and validates edits, promoting the reliability of the process across all operations.
• Sandbox Environment: Executes Git and testing operations securely, protecting credentials from exposure.
• Indexing and Storage: D1 indexes tasks, changes, and evidence, while R2 retains essential logs, transcripts, and screenshots for review.

Advantages of Cloudflare Integration

• Utilization of Workers for gateway management, user interface, and integration services close to the coordination API.
• Durable Objects combined with SQLite for a single, authoritative log per repository, enhancing data integrity and coordination efficiency.
• Workflow Systems allowing durable and retryable processing of revisions, testing, selection, and more.

Explore Further

To begin exploring Weft, follow the installation guide to set up the toolchain locally, conduct a protocol conformance suite, and, if desired, deploy a preview using individual Cloudflare accounts—all without requiring any provider credentials during the local setup.

Repository Structure

• packages/protocol — Contains WCP types, schemas, validators, and reference coordinators.
• packages/analyzer — Features TypeScript tools for diff-to-symbol analysis.
• packages/adapters — Houses translators for harness-specific hooks.
• apps/gateway, apps/workflows, apps/sandbox, apps/web — Provide coordination APIs and user-facing applications.
• demo/ — Includes various scenarios and evidence collection tools.
• docs/ — Comprehensive design documents, protocol specifications, and proposals.