https://www.boundaryml.com logo
also just to reiterate a couple points
# studio-beta-feedback
a
also just to reiterate a couple points of feedback (1) would be nice to have the call stack completely gone when stacksize==1 (which for me it is since not using traces currently), and also some way to more easily access LLM Request section - if my parameters include a list of dozens of chat messages then i have to scroll halfway down the panel to see this section - and to me thats the section i care most about, often the only thing i want to see, 2nd thing i care to see is (raw) response idk about other people who might have different usage patterns but the structured INPUTs are far less relevant to me that the perceived input i.e. actual raw string input. https://cdn.discordapp.com/attachments/1406858241337593876/1465845129259646996/image.png?ex=697b3ee8&is=6979ed68&hm=3b9c9d33f68c6fff334db121298c7f1fa8beb9ee33997d93569ad7cdece77c4d& https://cdn.discordapp.com/attachments/1406858241337593876/1465845129532149884/image.png?ex=697b3ee8&is=6979ed68&hm=c349150a219987d043841baad14381041d2e3ba8d1cdd97d95863baf464f04f2&
a
yess we did do this but ran into some other UI issue. You can make this particular panel very small by dragging, and it will remember your setting. I'll bring back the UI fix though
ah gotcha, i'll think about removing the structured input and just keeping things simpler
Changelog (deploying in an hour or so): 1. if toplevel function is an llm, we dont render call stack 2.
input
and
output
boxes now have a max size, and will have a scroll bar. 3. If the panel is large enough, it will render llm request and response side by side 4. URL deeplinking had some bugs where we couldnt load the trace or loaded the incorrect trace. 5. Missing message in the
LLM Request
view is now fixed. It happened when there was
metadata
like the anthropic
cache options
https://cdn.discordapp.com/attachments/1465845129691795549/1468393365966946434/image.png?ex=6983db63&is=698289e3&hm=eff5a21126e78d870b82cca8f0c0cd7884dfa8c51a965b775d20c6bd06bb5cf1&
2 Views