The main itch I wanted to scratch for my own exploration with chatgpt was that I found myself doing a lot of curl requests, and then after a few iterations I would come up with one that worked well. The next step was to reproduce that last result (without ideally hitting the openai servers again) and I wanted to pipe it to the next part of my chain.
This project kind of grew out of that. Every time I had more than 2 pipes I created a new "ease of life" parameter.
Although it is possible (and likely) that your working memory is far greater than mine to come up with a command like that.
I am sure I could encode stuff with plain other tools as well, but jq is actually handy for escaping json strings. And since it can read variable content from stdin, I was a happy man. Even with decently working emacs integration now.
But again, thanks for writing this. I have both now, and will happily steal ideas from chatblade!
The dream is ultimately to leverage chatgpt as a fuzzy text assistant to 10x productivity and I think combining the unix CLI which is optimized for text is the best way to do so.
It is also one of the great powers of the unix CLI that there are many roads that lead to rome.