Writ coordinator v1.0.0

The first tagged release of the self-hosted Writ coordinator.

The version matches writ-agent v1.0.0
and writ-mcp 1.0.0. The coordinator,
the agent it drives and the connector that talks to it are one product and are
versioned together, so "which agent goes with which coordinator" is never a
question you have to research.

Getting started

git clone https://github.com/usewrit/writ.git && cd writ
./scripts/gen-env.sh
docker compose up -d --build

Open http://localhost:8000, create the owner account, then connect an agent from
Fleet — the page prints a one-line installer that fetches the published
writ-agent release for your platform and verifies its SHA-256 before running it.

Full setup, deployment and operations documentation is in the
wiki.

What is in it

A single-owner coordinator you run yourself: browser workflows recorded once and
replayed with no model in the loop, site crawling with PDF/office/OCR extraction,
change monitoring, a REST API over everything, and a 31-tool MCP server so an AI
client can drive it directly. SQLite on disk, secrets encrypted at rest, no
outbound telemetry.

See CHANGELOG.md for the complete list.

How this release was verified

Beyond per-component CI, every release is gated by scripts/release-e2e.sh,
which walks the whole promise across repository boundaries:

docker compose up → coordinator + doc-extract healthy → create the owner →
mint an API key → install the published agent release through the same
one-liner the UI prints, checksum verified → agent connects to the fleet →
record a workflow on a real browser over MCP → replay it → call it over REST →
call it over MCP.

You can run it yourself: ./scripts/release-e2e.sh.

License

AGPL-3.0. GET /api/about reports the running version and where its source
lives, as §13 requires; operators of a modified build point WRIT_SOURCE_URL
at their own fork.