Enable device workflow by default and unify physical device deploy#11
Merged
maatheusgois-dd merged 1 commit intoJun 5, 2026
Merged
Conversation
Agents could not discover device tools and build_and_run was simulator-only; this makes device deploy first-class with better doctor checks and install retry guidance. Co-authored-by: Cursor <cursoragent@cursor.com>
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
maatheusgois-dd
marked this pull request as ready for review
June 5, 2026 21:43
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
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
deviceto default MCP workflows so agents see physical device tools withouttoggle-workflow device onbazel_ios_build_and_runwithplatform: deviceplusdeviceId/deviceName, sharing deploy logic withbazel_ios_device_build_and_runbazel_ios_device_get_app_path, session defaults for device fields, and structured install-failure responses with retry hintsbazel_ios_healthwith devicectl connectivity, codesigning identity count, workspace env warnings, and both UDID formats inlist_devicesScope
Validation
npm run lintnpm run typechecknpm testnpm run buildnpx vitest --run --coveragexcodebazelmcp ...Compatibility
Notes For Reviewers
Default advertised tools increase from 38 → 52 (device workflow +
bazel_ios_device_get_app_path).New shared deploy path:
src/core/device-deploy.ts(deployBuiltAppToDevice). On install failure after a successful build, tools return structured{ build: "ok", appPath, bundleId, retryTools }plus mapped errors for locked/untrusted/signing cases.Example device run after this lands:
Follow-ups not in this PR:
bazel_ios_device_preflight, Bazel server lock detection, rules_xcodeproj output path fixes, monorepo skill updates.Made with Cursor