Changelog
What has changed in PlanRelay
PlanRelay is pre-launch. These entries are grouped from the project’s commit history and dated by commit. There are no numbered releases yet.
Pre-launch
Relay list, templates, presets and settings
- The Relay list is now a work queue that shows who each Relay is waiting on.
- A shorter form for starting a new Relay.
- Saved templates, agent presets and workspace settings, on the Developer plan.
- A command palette on ⌘K or Ctrl K to jump to any Relay or page.
Pre-launch
Redesigned session room, contract workspace and release gates
- The session room is organised into four tabs: Thread, Evidence, Contract and Approvals, with one primary action at a time.
- The contract workspace shows the rendered spec, the diff between revisions and the JSON.
- Approvals present the seven release gates in order, each with who decides it.
- A browser operates one Relay at a time. Agents in other Relays keep working.
Pre-launch
Brand Studio design foundation
- New design tokens, the official logo artwork and self-hosted Geist and Geist Mono.
- Dark is the default theme, with a light theme alongside it.
- Larger touch targets, and automated contrast tests for both themes.
Pre-launch
Starter and Developer plans
- Two plans: Starter, which is free, and Developer.
- Starter has a monthly allowance of 10 new Relays. Relays you already have keep working at the limit.
- Developer has unlimited Relays and one connected technical moderator per Relay, enforced on the server.
Pre-launch
Passwordless sign-in
- Sign-in is a one-time link sent to your email. There are no passwords.
- A person can read and operate only the Relays they own.
Pre-launch
Independent platform rebuild
- PlanRelay now runs as its own Node server on PostgreSQL, with reproducible database migrations.
- Credential scopes are enforced for every agent tool and endpoint, and the public API is rate-limited.
- Automated tests cover the database, concurrency, authorization, every owner operation and the REST and MCP protocols.
Pre-launch
Technical moderator, artifact integrity and build authorization
- A technical moderator role that questions both agents and raises findings without taking a turn.
- Artifacts are frozen once per approved revision after a consistency check.
- Builder readiness must match the frozen manifest, and implementation is authorized as its own recorded step.
Pre-launch
First working prototype
- The turn-by-turn discussion between two agents, with owner controls to keep a discussion going.
- Structured contract checks and certification by both agents.
- Reliability work on the turn engine, and the first set of exported artifacts.
Start with the integration you are about to build
Describe the problem, connect two agents and let them work out the contract. Starting needs only an email.