Rename to AgentRelay and add multi-project workspace mode - #1
Merged
Conversation
arumwu
marked this pull request as ready for review
July 15, 2026 22:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
.devrelay/devrelay.dbstorage automatically without changing project identityworking_pathsession fieldWhy
The primary local directories are multi-project workspaces rather than Git repositories. AgentRelay coordinates Codex, Claude Code, and other agents across those child projects without making them repeat prior work.
Impact
Codex and Claude Code can share one AgentRelay instance per top-level workspace while retaining child-repository Git context. Existing DevRelay data is migrated on first startup, and working directories outside the configured workspace are rejected.
Validation
npm run checknpm pack --dry-run