eugenegusarov

I would definitely like to avoid that for now. It's just me for now.

As far as I understand it's a much more robust syntax that allows complex logic?

You're absolutely right. Currently they are not stored. This is one of the things that are on my short list.

Get to a sales call with Velum, Basalt and others to find out.

It's not OpenSource yet. Do you think it should be?

API calls are routed through a thin proxy on my side, this is how you get access to all the models with my API keys. I definitely would not want to store those keys in code of the JS bundle in the browser (:

Is this a full screenshot of the page? You can not only collapse the panel, you can also resize it in a way you want. Just drag the top edge of the panel.

In terms of calls to LLMs. I do not use any frameworks or LLM proxies like OpenRouter etc. Instead, I make the calls directly to LLM providers with a tiny thin proxy endpoint I created in Supabase.

One of the problems I had with other tools was the difficulty in understand the actual responses that particular playgrounds provided. Especially when it came to error responses. I guess that they are either built with the some Proxy providers like OpenRouter who handles and interprets errors internally before giving a response to the user, or they are using frameworks like LangChain with their abstraction hell.

In our case on Yola, it was crucial to have a playground that provided this raw type of experience that I have builtin.

For sure, man. This is absolutely unexpected. I will check what went wrong and fix the issue.

Do you have a link? I'd like to see it.

Any specific feedback so far?