Current stageR12-R20 local foundations
Live development scope

What is in motion now

updated from the public state
  • R4.1-R10Protocol + conformanceGuarded / conforming
  • R12Worker boundaries + permission receiptsImplemented locally
  • R13A2A / ACP transport + adaptersImplemented locally
  • R14Model Atlas + usage ledgerImplemented locally
  • R15Control rooms + private projectionsImplemented locally
  • R16Library intake + progressive onboardingImplemented locally
  • R18Trusted devices + recoveryFoundation / gated
  • R19Authenticator + mobile approvalsFoundation / gated
  • R20Multi-authority queues + routingFoundation / gated
  • M5Hosted tenancy + external operationsNot enabled

Green means the local contract or conformance work is implemented. Yellow marks a foundation whose production boundary is still gated. Red means the capability is intentionally not enabled.

Menu
Help when the boundary matters

Need Help?

Start with the local troubleshooting guide, then open a public issue with the smallest safe reproduction. Private transcripts, credentials, and sensitive workspace files do not belong in public tickets.

Report an issueRead updatesDownload Relay
Before opening a ticket

Make the problem reproducible and safe to share.

Include the Relay version, Windows version, exact command or screen, whether the workspace is local or synced, and the smallest synthetic reproduction. Redact paths, tokens, account names, private transcripts, and raw credential stores.

Optional project support

Want to help keep Relay moving?

Visit the dedicated support page for GitHub Sponsors, Ko-fi, the project story, and the other public-interest projects behind this work.

Support the project →
Common first checks

Work from the least destructive explanation.

Installer or SmartScreen prompt

Check the downloaded file path, version, and Authenticode status. Current local candidates may be unsigned; do not treat a SmartScreen warning as proof of infection or safety.

Release and signing notes →

Archive does not appear

Confirm the active workspace, check whether it is locked, and use Archive preview before importing. Source files are not modified by the normal intake path.

Archive FAQ →

Tool or connector failure

Separate detection from authorization. Capture the connector name, schema or manifest digest, bounded error, runtime version, and whether the action was a dry run.

Evidence boundary →

OneDrive or sync conflict

Pause sync before forensic comparison, preserve a copy, and do not delete suspicious files solely because a sync client reports a reparse or metadata anomaly.

Privacy and source boundary →
Public intake

Issue templates now; private support later.

Use GitHub Issues

Bug, documentation, or feature request

Choose a template and include only public-safe diagnostic information. The repository is the current auditable ticket record.

Open issue templates
Planned support service

Private tickets and account support

A hosted ticketing system would require identity, retention, deletion, abuse handling, and private-data controls. It is not silently represented as available today.

Not enabled
Community / forum

Discussion space when moderation exists

GitHub Discussions can become the public forum once moderation, code-of-conduct, security-report routing, and archival rules are in place.

Open Discussions →