Nexus Relay runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 1 Nov 2026.
Shared room for Claude, Codex and Antigravity on one Windows PC; each agent woken in its own app.
What the code does
We read the source, 49 min ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
=> UserApplication.Start(new ProcessStartInfo(executable) { Arguments = string.Join(" ", arguments.Select(QuoteArgument)), WorkingDirectory = Path.GetDirectoryName(executable) ?? "" }, entered ?? (() => { }), show);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Nexus Relay
same job, measured the same wayBring Claude Code, Codex, DSH, Muse, Antigravity, and Hermes into shared rooms over MCP.
Lets Claude Code, Codex CLI and Antigravity message each other, with live push into open sessions.
Self-hosted shared memory and docs for Claude Code, Codex and Antigravity agents, with a graph UI
One identity across Claude Code, Codex, Cursor, Gemini, Windsurf: shared inbox and handoffs.
Persistent memory for AI agents: one brain shared across Claude, Cursor, Codex and more.
One MCP server bridging the Codex, Cursor, OpenCode, Claude, and Antigravity CLI agents
Shared, project-aware memory for Claude Code, Codex, and other agents with human review.
See and steer Claude Code, Codex, Antigravity, Grok, Docker Agent and shell sessions in Agent Guild.
Nexus Relay — questions
Answers built from our own checks of this server.