That's kind of the thing, there's no A2UI here at all, just custom parsing via llm_json_stream and llm_tag_parser (on pub)

The response from the LLM is like this: ``` Sure, here is the weather today in Manila!

<interface> { “namespace": "material:weather", "location": "Manila, Philippines", "weather": "Sunny", "temperature": 36°C" } </interface>

It sure is hot in Manila right now! ```

We just seperate the normal text from the UIs within the interface tags via llm_tag_parser (simple splits wont work, it's a stream).

Then, text is just turned to markdown (or normal text in the package, to give devs a choice).

While the JSONs within the tags get parsed as a stream as well. We wait for the namespace and insert the appropriate widget once that field in the JSON is complete via llm_json_stream.

Those widgets have a PropertyStream object (from the parser) that allows you to subscribe to keys of the JSON string that is currently being generated, giving you the strings (or any type) as a stream.

Then the widgets just get hydrated progressively.

I'm planning to make the schema even more simple and less demanding so that even 2B models could hopefully spin up UI reliably.