Fix broker precedence for relay MCP injection#260
Conversation
|
Warning Review limit reached
Next review available in: 22 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Code Review
This pull request updates resolveAgentRelayBrokerBinary to prioritize the BROKER_BINARY_PATH environment variable over AGENT_RELAY_BIN and introduces unit tests to verify this behavior. Feedback on the tests suggests avoiding hardcoded fallback values that could cause environment-dependent failures, recommending instead to assert against the result of calling the function with an empty environment.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d5fc4d8064
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
All reported issues were addressed across 1 file (changes from recent commits).
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Summary
BROKER_BINARY_PATHAGENT_RELAY_BINas the legacy broker fallbackWhy
Pear workers now separate the native broker path from the external Agent Relay cloud CLI. The runtime builds
mcp-args --registerfor the broker binary, but previously selectedAGENT_RELAY_BINfirst. When both variables were present, it could invoke the cloud CLI for a broker-only command.Red-first coverage
Before implementation, the new regression test failed with:
/opt/agent-relay/opt/agent-relay-brokerThe test file now proves:
Validation
pnpm install --frozen-lockfilepnpm -r build— greenpnpm run lint— greenpnpm run typecheck— greenpnpm --filter @agentworkforce/runtime test— 103/103 greengit diff --check— greenRepository-wide
pnpm run testwas also attempted. The runtime and other completed packages were green, but the pre-existing@agentworkforce/clilocal-personas suite failed 34 unrelated cascade tests against the currentorigin/maincontent on this macOS host. This PR does not touch CLI persona loading; hosted CI remains the authoritative full-suite gate.