@jasonlk "Resolve a ticket" is in a particular niche where you have really high volume but also very discrete events that are worth paying for. Is the generalized form of this "one human-initiated session"? What about offline processing?
@GergelyOrosz We need a language similar to API design but for deciding where my agent ends and yours begins. Clearly a domain-specific prompt + context fetching layer is valuable in many cases.
Just launched the most significant open source project of my career, very excited!
Eraser diagrams is an end-to-end tool for generating diagrams with the help of LLMs (or fully programatically, if you put in some work!).
The stock library supports a wide array of visual options (borders, colors, alignment, our lovely watercolor style) and custom color palettes so that you can refer to "brand-blue-5" in your diagrams and have it just work.
For deeper customization, you can even define your own components; they're just HTML + CSS + JSON Schema. If it conforms to the diagramming protocol, it'll plug right in - just refer to the component by tag in your diagram.
The worst thing about agents is that they make you a worse writer because they accept and (pretend to) understand sloppy, lazy requests that you'd be embarrassed to send to a colleague.