Repository navigation
fix(engine): size the connect plan at 10M api_calls - #563
Conversation
A Connect room can hold 10 seats for up to 7 days, and each joined seat polls its inbox every few seconds. At 3M calls a full room would run out of quota before it expires, so connect now matches pro's monthly call budget while keeping its lower agent, message, file and rate limits. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
khaliqgant has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 5
✨ Finishing Touches
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.
🔍 Devin Review: 1 flag
Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
khaliqgant has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
Part of AgentWorkforce/cloud#5293, following review on AgentWorkforce/cloud#5296.
Problem
connectallowed 3Mapi_callsa month while Cloud allowed rooms to live 30 days. A joined seat polls about 22 times a minute, so a full 10-seat room makes about 220 calls/min, about 317k a day: roughly 9.5M over 30 days, past 3M. Cloud now caps rooms at 7 days (AgentWorkforce/cloud#5334), which bounds a full room at about 2.2M; 10M is the approved limit and leaves headroom for faster polling or retries.Change
PLAN_LIMITS.connect.api_calls: 3,000,000 → 10,000,000 (equal topro). Agents (10), messages (100k), files (1 GiB) and rate (1,200/min) are unchanged and stay belowpro.api_callsto equalpro; the other metrics stay strictly below.[Unreleased - Patch]).Approved by Khaliq (10M and a 7-day room cap).
Verification
🤖 Generated with Claude Code
Note
Low Risk
Single numeric entitlement change with test and doc updates; no auth or billing logic beyond static plan limits.
Overview
Raises the
connectworkspace plan monthlyapi_callsquota from 3M to 10M inPLAN_LIMITS, matchingproso Relay Connect rooms with heavy inbox polling (e.g. a full 10-seat room for a 7-day cap) stay under plan limits. Agents, messages, file caps, and rate_per_min are unchanged and still sit belowpro.StaticEntitlementsProvidertests now expect 10M forconnectand treatapi_callsas allowed to equalprowhile other metrics remain strictly betweenfreeandpro. Root and engine changelogs ([Unreleased - Patch]) and the README plan table document the new limit.Reviewed by Cursor Bugbot for commit 0557067. Bugbot is set up for automated code reviews on this repo. Configure here.
Need help on this PR? Tag
@codesmith-botwith what you need.Local full engine suite and
tscwere not usable on this machine:Could not locate the bindings fileforbetter-sqlite3under Node 26.8.1, andCannot find module '@relaycast/types'because the workspace packages are not built in this fresh worktree. CI'sLint, Build & Testis the gate.Agent Relay sessions
claudesession3e515a05· opened viagh pr create· last active 2026-10-18