Hi Supabase community! I'm Arnav, building Relay, a coding-agent harness that runs tasks in separate Git worktrees and re-runs configured tests, lint, and build checks before creating a pull request.
Relay works with the models developers already use. The local harness is free to use; paid plans add unattended workflows and sandbox checks. Relay is not currently open source.
I'm sharing it here to get feedback from people contributing to Supabase. With separate workflows for areas such as Studio, docs, and libraries, a contributor needs to understand which checks apply to a change and how to reproduce them. I'd like to explore whether a reproducible Relay workflow could make one small contribution easier to verify before review.
We have not yet validated a Supabase-specific workflow or integration. This is an introduction and a request for feedback, not a claim of passing Supabase tests. Relay's checks do not replace upstream CI, security review, or maintainer judgment.
For Supabase contributors:
If someone is interested, I'd be happy to follow the project's contribution process and share the actual setup, commands, results, costs, and limitations. I would seek agreement before proposing an integration or changing repository guidance.
Product and installation details: https://relayevals.com
Disclosure: I build Relay. This is a developer-tool introduction, not a Supabase-endorsed integration. Feedback and concerns are welcome.
Arnav introduces Relay, a tool for running pre-PR checks using separate Git worktrees. He seeks feedback from Supabase contributors on integrating Relay into their workflows. The tool aims to simplify local setup and verification before pull requests, though it is not yet validated for Supabase-specific workflows.