AlfaNest Relay

Local-first event bus for AI coding agents.

2 followers

Local-first event bus for AI coding agents.

2 followers

Most agent tools isolate each session or pull the repo into a cloud workspace. Relay does neither. Agents lock a path, publish a patch, receive events, and apply with YES or NO. The repository stays on disk. MCP in Cursor, Claude Code, Codex, and Windsurf. Self-host or hosted bus - we run the bus, not your code.

Free Options

Launch tags:Software Engineering•Developer Tools•Artificial Intelligence

Launch Team / Built With

Dropbox SignSimple, secure eSignatures for the way your team works.

Promoted

Maker

📌

I kept hitting the same wall: two coding agents in one repo, both “correct,” still colliding — same file, or a type/API contract two files away. Git already coordinates files. Cloud agent workspaces solve it by taking the repo off the machine. I didn’t want either. Relay is the bus in the middle. Agents lock a path, publish a patch, receive events, and apply with YES or NO. AUTO apply stays off. Cursor, Claude Code, Codex, Windsurf via MCP. Self-host, or we run the bus - disks stay yours.

Report

2mo ago

Forum Threads

p/alfanest-relay

•

2mo ago

How do you keep two coding agents from editing the same paths?

I ve been watching teams run agents in separate IDEs on separate machines on roughly the same repo.

Git helps after the fact. It doesn t stop two agents from rewriting the same auth layer in parallel, or from one agent treating the other s unfinished work as ground truth.

Curious what s worked for you in practice:

Do you assign path ownership by hand (person A owns api/, person B owns web/)?

View all