streamdown

My streaming markdown renderer does something like that https://github.com/day50-dev/Streamdown You define a baseline color in HSV and then everything else is a multiplier of that For example [style] HSV = [0.7, 0.5, 0.5] Dark = { H = 1.0, S = 1.2, V = 0.25 } # Make dark elements less saturated and darker Symbol = { H = 1.0, S = 1.8, V = 1.8 } # Make symbols more vibrant As a result you can simply move around the HSV to your preference in the config and things don't look like garbage where you have to hand tweak every color to get something legible. For example, this simple loop https://github.com/day50-dev/Streamdown?tab=readme-ov-file#c... It's effectively a swatch

This exact problem is why I wrote Streamdown https://github.com/day50-dev/Streamdown Almost every model has a slight but meaningfully different opinion on what markdown is and how creative they can be with it. Doing it well is a non-trivial problem.

It's worth noting the streaming markdown renderer I wrote just for this tool: https://github.com/day50-dev/Streamdown More background: https://github.com/simonw/llm/issues/12 (Also check out https://github.com/day50-dev/llmehelp which features a tmux tool I built on top of Simon's llm. I use it every day. Really. It's become indispensable)

I've got a similar approach from a Unix philosophy. Look at the savebrace screenshot here https://github.com/kristopolous/Streamdown?tab=readme-ov-fil... There's a markdown renderer which can extract code samples, a code sample viewer, and a tool to do the tmux handling and this all uses things like fzf and simple tools like simonw's llm. It's all I/O so it's all swappable. It sits adjacent and you can go back and forth, using the chat when you need to but not doing everything through it. You can also make it go away and then when it comes back it's the same context so you're not starting over. Since I offload the actual llm loop, you can use whatever you want. The hooks are at the interface and parsing level. When rendering the markdown, streamdown saves the code blocks as null-delimited chunks in the configurable /tmp/sd/savebrace. This

Well hopefully my current thing, a streaming markdown renderer for the terminal (https://github.com/kristopolous/Streamdown) hasn't also been a waste of time

streaming markdown renderer in the terminal. As far as I know, the only one in existence that works like this, which is why i felt compelled to write it: https://github.com/kristopolous/Streamdown

They're sophisticated tools at much as any other software. About 2 weeks ago I started on a streaming markdown parser for the terminal because none really existed. I've switched to human coding now but the first version was basically all llm prompting and a bunch of the code is still llm generated (maybe 80%). It's a parser, those are hard. There's stacks, states, lookaheads, look behinds, feature flags, color spaces, support for things like links and syntax highlighting... all forward streaming. Not easy https://github.com/kristopolous/Streamdown