RelayWork
Get started free →
FeaturesLearnGlossaryPricingChangelog

Changelog

What shipped, newest first. Every workspace also gets its own changelog page for its own customers — this one is ours.

Agents can anchor a spec to code

  • New MCP tool add_code_ref: an agent attaches GitHub permalinks with a note and a kind, in one batch, and each ref reports whether it was added, rejected or already there.
  • get_spec now returns the refs already on a spec, so an agent stops re-proposing the same ones.
  • A new spec defaults to its creator as owner. An unowned spec has nobody to chase.

Linked code refs

  • Code attached to a spec is now a record, not markdown: a Code section listing GitHub permalinks pinned to a commit, each expanding to the source inline.
  • Refs can be tagged blast radius — code the work could break but does not touch.
  • A draft PR syncs the files it touches onto the spec, and re-syncing preserves notes a human wrote.

Implementation specs are written from real code

  • The implementation-spec stage is now Exploring: read the code and open a draft PR with stubs, then write the document from what you found.
  • Draft PRs link to a spec and seed it, but never advance a gate. Marking a PR ready for review is what moves the work on.
  • Source behind a ref is served at the commit it was pinned to, so a card keeps showing the code the decision was made against.

Typed issues, house templates, named reviewers

  • Issues carry a type — feature, bug, tech debt, chore or request — and a priority, with a tech-debt view that finally makes the backlog honest.
  • Requirements use a seven-question house template, and the implementation document stays locked until requirements are approved.
  • Reviews go to named people: "waiting on Priya, asked by Sam", with the age of the request in days.

MCP: Claude writes into the gates

  • Streamable-HTTP MCP endpoint with workspace API tokens, read and write scopes, and revocation.
  • Eleven tools and no approve tool. Machine writes are attributed to the token, never to a teammate.
  • Stage changes accept any target: forward walks the gates hop by hop and audits each one; backward is a single audited step.

Sign in on your own domain

  • Native Google sign-in, then Microsoft — no third-party identity detour.
  • Dashboard rebuilt around your work: what is yours, what is waiting, what shipped this week.

Notion-style docs

  • A real editor: slash menu, nested pages, private-by-default notes, [[wiki links]] with backlinks.
  • Markdown underneath, autosave, and a conflict guard so two people cannot silently overwrite each other.

Specs and approvals

  • The gate ladder: requirements and implementation documents, versioned approvals, review notes bound to a version, and an append-only audit trail.
  • Editing an approved document supersedes its approvals and returns the spec to review.
  • Risk tiers: higher-risk work asks for a second approver.

Invite your team

  • Admin-gated invites with resend and revoke, and a public accept link that resolves the workspace from the token.

Self-serve signup

  • Create a workspace on your own subdomain, verify by email, and land signed in.