:kodee_loading: Who is successfully using Compose...

# compose

[darkmoon_uk]

kodee loading Who is successfully using Compose Previews as feedback for AI Agents via vision models?
This must be something that people are doing already? Any MCP servers to share?

[yschimke]

Claude works really well

I wrote a library for this

https://github.com/yschimke/compose-ai-tools/

[yschimke]

https://github.com/yschimke/skills

[darkmoon_uk]

Amazing! Exactly the kind of response I was hoping for. Thanks, I'll check it out.

[yschimke]

It's pre-1.0, so raise bugs if you find any. Stick on a version that works if an upgrade breaks you.

[yschimke]

It's useful in a bunch of ways

• Increase quality of Agent PRs with evidence in the description (https://github.com/joreilly/Confetti/pull/1680)
• For matching against existing screens or Figma, it let's is iterate the the right design
• automate (non AI) review comments with changes introduced by the current PR

[yschimke]

There is a CLI which works for the typical cases, but also a MCP Server/Daemon that let's it do interactive testing (click and see effect) or extract data like A11y

[yschimke]

I've got each main build in github publishing a fresh baseline e.g. https://github.com/yschimke/compose-ai-tools/tree/compose-preview/a11y/main

[Nikita Lipsky]

We are going to release Compose Hot Reload 1.2.0-alpha01 with the MCP server this week. We would greatly appreciate any feedback on this matter.

[yschimke]

That's amazing. Any chance that comes to Android?

[Nikita Lipsky]

That's amazing. Any chance that comes to Android?

We are considering it but I can't promise you anything

[darkmoon_uk]

While Compose Hot Reload has many great uses; I don't think it quite replaces what @yschimke has built - for the use-case of having an agent visually verify its drafted UI designs; a Compose Preview bridge is more ergonomic right?

For the simple reason it's easy to nominate a specific view we're analysing. To achieve that in Hot Reload we'd need to build and operate a supporting runtime vertical and navigation system.

[darkmoon_uk]

Or @Nikita Lipsky is Compose Hot Reload designed to work with Previews as well, in some way?

[Nikita Lipsky]

I believe that the tools are complimentary. If you work on visual aspects of a specific view I agree that more focused tool can be beneficial. On the other hand, an agent may verify more global-wise changes with CHR.

is Compose Hot Reload designed to work with Previews as well, in some way?

It can be extended to work with Previews as well for MCP server. I am thinking of headless tools that an agent may use to verify things. Actually that tools may have a composable as an input parameter.

CHR has @DevelpomentEntryPoint annotation that has a similar purpose as @Preview - start an app from a specific composable. Moreover we have a feature request to make the things even closer.

[yschimke]

I really hope you go that way. Not all agent flows need to be navigating around an app. Maybe it's just seeing what changes in a pr, and once you have the evidence or nothing, asking the agent to review the code changes with those visuals.

[darkmoon_uk]

@yschimke I hit an unexpected problem while using your plugin: JetBrains Compose Multiplatform plugin and compose-ai-tools both register a Gradle task named discoverPreviews causing a`DuplicateTaskException`

[darkmoon_uk]

Unless I'm mistaken you might want to rename the task.

[yschimke]

Thanks for the heads-up. Will do. I can fix tomorrow.

[yschimke]

Feel free to raise an issue, but if not I'll try to find time

[yschimke]

@Chris can you provide a dump of tasks from the CMP plugin so I can see what to avoid?

[Nikita Lipsky]

We are going to release Compose Hot Reload 1.2.0-alpha01 with the MCP server this week. We would greatly appreciate any feedback on this matter

Here it is: https://github.com/JetBrains/compose-hot-reload/releases/tag/v1.2.0-alpha01

Please try it and share your feedback.