Scaffold iOS companion control architecture#1252
Open
heyramzi wants to merge 1 commit intostablyai:mainfrom
Open
Scaffold iOS companion control architecture#1252heyramzi wants to merge 1 commit intostablyai:mainfrom
heyramzi wants to merge 1 commit intostablyai:mainfrom
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR scaffolds the first backend architecture for an Orca iPhone companion app that can continue existing laptop sessions while the laptop remains the source of truth.
It adds:
RemoteControlServicescaffold that translates live Orca terminals into phone-manageable sessionsWhy this cut
The goal is to review the session identity, security, and transport boundaries before any SwiftUI or networking work lands.
The key architectural choice is that one remote session maps to one live Orca PTY leaf, not one repo or one worktree. That keeps remote continuation aligned with the exact agent conversation the laptop already has open.
Verification
pnpm exec vitest run src/main/remote-control/service.test.tspnpm run typecheck:node