Fix companion install QR and chat/workspace UX - #10
Conversation
LaunchAgents could not find `pi`, so the server died before printing the pairing QR. Resolve pi explicitly, set PATH in the LaunchAgent, and wait for the banner. Also assign Conductor-style city names on workspace create, drop session tabs, and move the model picker under the composer. Co-authored-by: Cursor <cursoragent@cursor.com>
|
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. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThe server now resolves Pi executables, stores user-facing workspace names, and improves LaunchAgent startup reporting. The mobile app adds structured API errors, workspace creation alerts, and revised chat controls. Conductor local settings are ignored. ChangesServer runtime and workspace flow
Mobile API and chat experience
Local configuration exclusions
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
✨ 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
piPATH resolution + agent PATH)Test plan
curl -fsSL https://raw.githubusercontent.com/MRL-00/pi-mobile/main/server/install.sh | bashprints listening line, auth token, and QRhttp://<mac>.local:8940+ token) pairs the phoneMade with Cursor
Summary by CodeRabbit