fix(acp-bridge,openclaw): use AgentRelay.spawnAgent instead of removed spawnPty#1007
Conversation
…d spawnPty The AgentRelay class no longer exposes spawnPty (it lives only on AgentRelayClient). The two remaining callers were using the unified spawnAgent facade was renamed during the #1003 spawn-provider work, so this restores the build for both packages.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
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 (2)
📝 WalkthroughWalkthroughThis PR switches two relay SDK spawn call sites from ChangesSpawn Method Migration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related issues
Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Summary
Fixes the failing CI build on
main(run 26520261748).After PR #1003 / #1006,
AgentRelayonly exposesspawnAgent—spawnPtylives only onAgentRelayClient. Two callers were still usingrelay.spawnPty(...)onAgentRelayinstances, which broke the TypeScript build of@agent-relay/acp-bridge(the visible CI failure) and would have broken@agent-relay/openclawnext.packages/acp-bridge/src/acp-agent.ts:739—relay.spawnPty(...)→relay.spawnAgent(...)packages/openclaw/src/spawn/process.ts:174— sameTest plan
npm run buildis green locally (all 19 turbo tasks)https://claude.ai/code/session_0181Fs6YPkrKrGeRQk3YFqi1
Generated by Claude Code