You might be confusing license with access. The product itself has a proprietary license. Even then, a majority of the libraries they produce are also available under the MIT license.

The way we elevator-pitch Tambo is "an agent that understands your UI" (which, admittedly, is not very descriptive on the implementation details). We've spent the time on allowing components (be that pre-existing or purpose-built) to be registered as tools that can be controlled and rendered either in-chat, or out within your larger application. The chat box shouldn't be the boundary.

Personally, my take on standards like A2UI is that they could prove useful but the models have to easily understand them or else you have to take up additional context explaining the protocol. Models already understand tool-calling so we're making use of that for now.

I can think of a few improvements that could be fun to see;

- visual indicator for chord progression

- timing/tempo/click track for practice

- play the chord via audio output

- verify the chord via audio input

On a higher level, this is the sort of app/experience that really opens up learning to a whole new audience, particularly if there's no easy or affordable access to instructors. Nicely done!