2 ms·
Wow, that library is looking really great! I think I want a plugin hook that lets plugins take over the display of content by the tool. Just filed an issue: h
by simonw 1y ago
Wow, that library is looking really great!
I think I want a plugin hook that lets plugins take over the display of content by the tool.
Just filed an issue: https://github.com/simonw/llm/issues/1112 https://github.com/simonw/llm/issues/1112
Would love to get your feedback on it, I included a few design options but none of them feel 100% right to me yet.
- kristopolous 1y agoThe real solution is semantic routing. You want to be able to define routing rules based on something like mdast (https://github.com/syntax-tree/mdast https://github.com/syntax-tree/mdast) . I've built a few hacked versions. This would not only allow for things like terminal rendering but is also a great complement to tool calling. Being able to siphon and multiplex inputs for the future where cerebras like speeds become more common, dynamic configurable stream routing will unlock quite a bit more use cases. We have cost, latency, context window and model routing but I haven't seen anything semantic yet. Someone's going to do it, might as well be me.