Since this is an opt-in feature, why is it not being considered for merging?

I agree, @vphantom, but @simonw has never responded to this PR or previous PRs/issues relating to this functionality. I tried contacting him on other platforms over many months as well, to no avail. Given that the contributions guide is there (and we followed it), it would be nice to get some kind of response, but this is open source and he's under no obligation to anyone.

The piping workarounds mentioned here only help in one-shot mode.

I use richify.py as a stop-gap solution (though it doesn't work in chat mode, as you mention). I still use it constantly and it annoys me every time that this isn't just a flag option in llm 😢

I've thought about just forking or re-writing llm with rich rendering functionality, but then I'd have to constantly update it to keep up with evolving models and APIs and I don't love the prospect of taking that on.

Someone once suggested trying to add the rich rendering functionality via plugins, but I suspect that to be an ass-pain.