refactor: remove legacy cloud sandbox IPC - #428
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
💤 Files with no reviewable changes (5)
📝 WalkthroughWalkthroughThe legacy ChangesCloud connection API cleanup
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested labels: Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Summary
BrokerManager.connectCloud()path that created an ad-hoc sandbox through Cloud's legacy/api/v1/sandboxesroutes.broker:connect-cloudIPC handler, preload API, shared type, renderer mock, and obsolete test mock.attachCloudSandbox/connectCloudSandboxpath used byCloudAgentManager.src/main/cloud-agent.tsunchanged.Companion Cloud work: AgentWorkforce/cloud#2894.
Verification
src/main/broker.test.ts: 110 passed.src/main/ipc-handlers.test.ts: 26 passed.connectCloud,broker:connect-cloud, or/api/v1/sandboxesreferences undersrc/.src/main/cloud-agent.tsis byte-unchanged.Environment notes
The repository-wide TypeScript and Electron build commands remain blocked by pre-existing unrelated diagnostics and a relocated
node_modulescache resolution issue. The affected broker/IPC suites were run directly; the IPC suite used Vite's symlink-preservation option so dependencies resolve from that existing cache.