Is there secret sauce that would make one better than the other? Available tools? The internal prompting and context engineering that the tool does for you? Again, assuming the model is the same, how similar should one expect the output from one to another be?
Crush: Glamourous AI coding agent for your favourite terminal
101–110 of 240 posts
Re: Crush: Glamourous AI coding agent for your favourite terminal
#102I find it strange how most of these terminal-based AI coding agents have ended up with these attempts at making text UIs flashy. Tons of whitespace, line art, widgets, ascii art and gradients, and now apparently animations. And then what you don't get is the full suite of expected keybindings, tab completion, consistent scrollback, or even flicker-free text rendering. (At least this one seems to not be written with n…
Re: Crush: Glamourous AI coding agent for your favourite terminal
#103Re: Crush: Glamourous AI coding agent for your favourite terminal
#104This is the most interesting feature IMO, interested to see how this pans out. The multiple sessions / project also seems interesting.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#105Re: Crush: Glamourous AI coding agent for your favourite terminal
#106Re: Crush: Glamourous AI coding agent for your favourite terminal
#107> LSP-Enhanced: Crush uses LSPs for additional context, just like you do This is the most interesting feature IMO, interested to see how this pans out. The multiple sessions / project also seems interesting.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#108I find it strange how most of these terminal-based AI coding agents have ended up with these attempts at making text UIs flashy. Tons of whitespace, line art, widgets, ascii art and gradients, and now apparently animations. And then what you don't get is the full suite of expected keybindings, tab completion, consistent scrollback, or even flicker-free text rendering. (At least this one seems to not be written with n…
> I find it strange how most of these terminal-based AI coding agents have ended up with these attempts at making text UIs flashy. Its next gen script kids.
Flashy stuff for the terminal it's not new. Heck, in late 90's/early 00's everyone tired e17 and eterm at least once. And then KDE3 with XRender extensions with more fancy stuff on terminals and the like, plus compositor effects with xcompmgr and later, compiz.
But I'm old fashioned. I prefer iomenu+xargs+nvi and custom macros.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#109Earlier quoted context omitted.
"the Charm stuff" it is built on (and anyone else can use) is :) And that's the stuff most of the industry (e.g. GitHub CLI) is using, btw. Also, it looks like Crush has an irrevocable eventual fallback to MIT[1] allowing them to develop in open so you basically get all the bells and whistles available. We probably couldn't ask for more :) [1] https://github.com/charmbracelet/crush/blob/317c5dbfafc0ebda...
That's a nice framework, does anyone else do that?
Re: Crush: Glamourous AI coding agent for your favourite terminal
#110I find it strange how most of these terminal-based AI coding agents have ended up with these attempts at making text UIs flashy. Tons of whitespace, line art, widgets, ascii art and gradients, and now apparently animations. And then what you don't get is the full suite of expected keybindings, tab completion, consistent scrollback, or even flicker-free text rendering. (At least this one seems to not be written with n…
Well this specific tool is by a company called Charm that has the mission statment of making the command line glamerous. They have been around for several years prior to the LLM craze. They make a CLI framework for golang along with tools for it.