Relay is an AI harness for coding agents built for long-running tasks. It supervises agents while you are away, resumes interrupted sessions, and recovers from failures. Relay runs on your machine with your existing repository and toolchain. It reads repository conventions, remembers session settings, runs configured tests, and produces signed receipts you can reopen and verify. Relay provides evidence about the configured checks; developers still review the code and decide what ships.
• Keeps long-running coding-agent sessions moving
• Resumes after interruptions and recoverable failures
• Uses your existing repository conventions and local toolchain
• Runs configured tests and verification checks
• Produces signed, re-checkable receipts
• Supports solo and team workflows
• Leave substantial coding tasks running unattended
• Recover interrupted agent sessions without starting over
• Validate changes with repository-native tests
• Review evidence before merging or shipping
• Maintain consistent workflows across developers and agents

The signed receipts you can reopen later are the part that stands out to me. Being able to come back and prove which checks ran while I was away is the trust problem with long agent runs. How does Relay handle a task that's halfway through a migration when it gets interrupted? Does it roll back or pick up from the last checkpoint?
Signed receipts for unattended runs make a lot of sense. One failure I've hit running several coding agents in parallel: two sessions on separate branches each picked the same database migration number, and each run passed its own tests. The clash only showed up after merging. Does Relay's verification run against the merged state, or only inside each session? A check like that is the one I'd most want a receipt for.

The signed receipts you can reopen later are the part that stands out to me. Being able to come back and prove which checks ran while I was away is the trust problem with long agent runs. How does Relay handle a task that's halfway through a migration when it gets interrupted? Does it roll back or pick up from the last checkpoint?
Signed receipts for unattended runs make a lot of sense. One failure I've hit running several coding agents in parallel: two sessions on separate branches each picked the same database migration number, and each run passed its own tests. The clash only showed up after merging. Does Relay's verification run against the merged state, or only inside each session? A check like that is the one I'd most want a receipt for.
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved