feat: add client metro prepare command#236
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
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
1 participant
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
Add
agent-device metro prepareas a client-side command that starts or reuses local Metro, optionally configures proxy bridging, and returns Metro runtime hints through the typed client API.Update CLI/docs/tests for the new command and keep Metro preparation isolated from daemon runtime internals.
Touched files: 11
Scope: stayed within the new metro client command family plus typed client exports and docs.
Known gaps/follow-ups: downstream sandbox consumers still need to switch from
agent-device-proxy metrotoagent-device metro prepare.Validation
pnpm formatpnpm typecheckpnpm test:unitpnpm test:smoke