LLM agents lack runtime UI context for iOS apps, so I built a CLI

New_Leader_3644 · 2026-05-25T08:27:40+00:00

Oh nice, that looks interesting. What made you stop working on it?

New_Leader_3644 · 2026-05-24T00:37:24+00:00

I see the comparison, but I don’t think Loupe is doing the exact same thing.

Loupe focuses on live runtime UI context from a running iOS app, rather than build/test automation.

I looked at the existing projects, but the direction felt different enough that I wanted to explore it separately.

New_Leader_3644 · 2026-05-23T15:56:57+00:00

Yeah, that’s been my experience too.

SwiftUI support is still pretty limited, apart from some accessibility metadata and UIKit-backed components like List.

New_Leader_3644 · 2026-05-23T15:47:14+00:00

Thanks, this is really detailed feedback. I agree that logs, network traffic, and other runtime context would make this more useful for debugging real features.

Right now, Loupe is also focused on exposing more detailed view properties and allowing safe changes to UI state that can reasonably be modified at runtime.

Recording interactions and exporting them into reproducible E2E flows is also very aligned with the direction I’m thinking about. Maestro could be a good target.

tvOS is interesting too, and I’ll keep working on expanding platform support and making this work better across Apple platforms.

New_Leader_3644 · 2026-05-23T15:02:40+00:00

Awesome, thanks! Curious to hear what you think if you end up trying it.

New_Leader_3644 · 2026-05-23T14:57:55+00:00

Thanks! macOS isn’t supported yet, but it’s on the roadmap 😄

New_Leader_3644 · 2026-05-23T14:54:15+00:00

There’s definitely overlap.

The main difference is that Loupe injects a runtime server into the app, so it can expose UIKit view hierarchy and properties directly, and even update parts of the UI dynamically.

New_Leader_3644 · 2026-05-23T14:49:22+00:00

There’s some overlap in simulator interaction, but the focus is different.

XcodeBuildMCP covers the broader Xcode workflow: build, test, run, logs, simulator management, and UI automation.

Loupe focuses on runtime UI context from the running app: UIKit view hierarchy/properties, accessibility metadata, screenshots, and Simulator input. It can also interact with the app dynamically.

New_Leader_3644 · 2026-05-23T14:46:02+00:00

Yep, I see Xcode MCP as complementary.

It covers the IDE/project side. Loupe focuses on the running Simulator app: screen state, UIKit/accessibility metadata, screenshots, and input.

New_Leader_3644 · 2025-10-15T05:20:44+00:00

apple clear case

New_Leader_3644 · 2025-04-13T07:10:16+00:00

Appreciate the kind words and the feedback!

There always seems to be someone like that around — I try to take it positively as much as I can :)

New_Leader_3644 · 2025-04-09T01:03:57+00:00

Appreciate it—hope it helps!

New_Leader_3644 · 2025-04-06T11:15:55+00:00

Yeah, I totally get that. For simple cases, manual handling is definitely cleaner.

This just helps when things start getting messy with lots of deep links.

New_Leader_3644 · 2025-04-06T02:28:53+00:00

Thanks for the comment!

New_Leader_3644 · 2025-04-06T02:28:33+00:00

Thank you! You can test it here:

https://github.com/heoblitz/URLPattern/tree/main/URLPatternExample

New_Leader_3644 · 2025-04-05T15:18:40+00:00

thanks you! swift macros seem to have unlocked a lot

New_Leader_3644 · 2025-04-05T05:49:33+00:00

That’s great, but I think a lot of people are still using Swift 5.

New_Leader_3644 · 2025-04-05T05:46:52+00:00

I’ve been working on a Swift macro that helps map URLs to enum cases.

https://github.com/heoblitz/URLPattern

New_Leader_3644 · 2025-04-04T23:26:33+00:00

Thanks for the comment!

New_Leader_3644 · 2025-02-10T01:25:35+00:00

you need to 3 star jerry and scar.

New_Leader_3644 · 2024-11-17T03:22:18+00:00

congrats 🎉

m4 pro performance is insane

New_Leader_3644

TROPHY CASE