feat(connect): raise device limit to five - #8127
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
ApprovabilityVerdict: Not approved Macroscope's review found this PR not approvable — The change raises the production managed-tunnel provisioning ceiling from three to five, allowing additional devices for accounts without overrides. Although the diff is small and isolated, it changes a user-facing capacity policy and the gate controlling provisioning. You can add or adjust custom eligibility rules. Learn more. |
T3 Connect accounts currently allow only three devices.
Raise the default limit to five and update the existing limit test. Per-account overrides are unchanged.
Made with GPT-5.6 Sol in the Codex harness.
Note
Low Risk
Single constant change with matching tests; per-user overrides and limit-check logic are unchanged, only the default provisioning ceiling increases.
Overview
Raises the default concurrent managed tunnel cap for Connect users from 3 to 5 by changing
DEFAULT_MANAGED_TUNNEL_LIMITin relay’sManagedTunnelLimitsservice.ensureCapacitystill uses per-user rows inrelay_managed_tunnel_limitswhen present; only accounts without an override get the higher ceiling.The unit test that asserts rejection at the default cap is updated so expectations match 5 active tunnels.
Reviewed by Cursor Bugbot for commit 5dd7ca0. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Raise
DEFAULT_MANAGED_TUNNEL_LIMITfrom 3 to 5Increases the default managed tunnel capacity for users without an override. Updates the corresponding test in ManagedTunnelLimits.test.ts to assert rejection at the new limit of 5.
Macroscope summarized 5dd7ca0.