[Feature Request] Add simulator UI automation support for iOS testing

Status Fixed / completed
Reported on v2.1.201
Maintainer reply ✓ Yes — bcherny
Activity 4 comments · opened Jul 5, 2026 · closed Aug 17, 2026
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Bug Description
simulator UI automation during iOS testing fail from Fable to Opus

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.201
  • Feedback ID: 33dc8689-aa2b-4628-8f61-abfcd4e5e6ab

Errors

[]

View original on GitHub ↗

3 Comments

ceejayoz · 3 months ago

https://www.xcodebuildmcp.com/ is what you're looking for. This isn't and shouldn't be a Claude Code function.

t-wingert · 3 months ago

This is feedback on the Fable guardrails drop to Opus in the session, pointing out the circumstances that triggered it. On Jul 5, 2026, at 3:21 PM, Chris Sternal-Johnson @.***> wrote:ceejayoz left a comment (anthropics/claude-code#74593)
https://www.xcodebuildmcp.com/ is what you're looking for. This isn't and shouldn't be a Claude Code function.

—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you authored the thread.Message ID: @.***>

bcherny collaborator · 1 month ago

Thanks for the feedback. Driving the iOS Simulator is supported today:

If a specific step is failing on one model, please open a bug with the steps and the error you saw. Closing since the capability exists.

🤖 Generated with Claude Code

Showing cached comments. Read the full discussion on GitHub ↗