based
Crush: Glamourous AI coding agent for your favourite terminal
81–90 of 240 posts
Re: Crush: Glamourous AI coding agent for your favourite terminal
#82The big question - which one of these new agents can consume local models to a reasonable degree? I would like to ditch the dependency on external APIs - willing to trade some performance in lieu.
sst/opencode
But only a few models can actually execute commands effectively.. what is it, Claude and Gemini? Did I miss any?
Re: Crush: Glamourous AI coding agent for your favourite terminal
#83Woah I love the UI. Compared to the other coding agents I've used (eg. Claude Code, aider, opencode) this feels like the most enjoyable to use so far.. Anyone try switching LLM providers with it yet? That's something I've noticed to be a bit buggy with other coding agents
Bubble Tea has always been an amazing TUI. I find React TUI (which is what Claude Code uses) to be buggy and always have to work against it.
Agreed. Charm has a solid track record of great TUIs. While I appreciate a good DSL, I don't think React for a TUI (via ink) is working out well.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#84I 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.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#85I 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…
For what it's worth, this is exactly why I am working on Jean-Pierre[0], pitched as:
> A command-line toolkit to support you in your daily work as a software programmer. Built to integrate into your existing workflow, providing a flexible and powerful pair-programming experience with LLMs.
The team behind DCD[1] are funding my work, as we see a lot of potential in a local-first, open-source, CLI-driven programming assistant for developers. This is obviously a crowded field, and growing more crowded by the day, but we think there's still a lot of room for improvement in this area.
We're still working on a lot of the fundamentals, but are moving closer to supporting agentic workflows similar to Claude Code, but built around your existing workflows, editors and tools, using the Unix philosophy of DOTADIW.
We're not at a state where we want to promote it heavily, as we're introducing breaking changes to the file format almost daily, but once we're a bit further along, we hope people find it as useful as we have in the past couple of months, integrating it into our existing terminal configurations, editors and local shell scripts.
[0]: https://github.com/dcdpr/jp [1]: https://contract.design
Re: Crush: Glamourous AI coding agent for your favourite terminal
#86Earlier quoted context omitted.
All of Charmbracelet's open source stuff is Go-based, which supports a bunch of platforms.
This is not open source.
"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...
Re: Crush: Glamourous AI coding agent for your favourite terminal
#87It's "glamorous", even in UK English.
https://dictionary.cambridge.org/dictionary/english/glamorou...
Re: Crush: Glamourous AI coding agent for your favourite terminal
#88Earlier quoted context omitted.
Most of these agents work with any OpenAI compatible endpoints.
Actually not really. I spent at least an hour trying to get OpenCode to use a local model and then found a graveyard of PRs begging for Ollama support or even the ability to simply add an OpenAI endpoint in the GUI. I guess the maintainers simply don't care. Tried adding it to the backend config and it kept overwriting/deleting my config. Got frustrated and deleted it. Sorry but not sorry, I shouldn't need another cl…
> I spent at least an hour trying to get OpenCode to use a local model and then found a graveyard of PRs begging for Ollama support
Almost from day one of the project, I've been able to use local models. Llama.cpp worked out of the box with zero issues, same with vllm and sglang. The only tweak I had to make initially was manually changing the system prompt in my fork, but now you can do that via their custom modes features.
The ollama support issues are specific to that implementation.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#89Why not use Aider?
Aider is not agentic.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#90Earlier quoted context omitted.
Most of these agents work with any OpenAI compatible endpoints.
Actually not really. I spent at least an hour trying to get OpenCode to use a local model and then found a graveyard of PRs begging for Ollama support or even the ability to simply add an OpenAI endpoint in the GUI. I guess the maintainers simply don't care. Tried adding it to the backend config and it kept overwriting/deleting my config. Got frustrated and deleted it. Sorry but not sorry, I shouldn't need another cl…
I still haven't seen any local models served by Ollama handle tool calls well via that OpenAI endpoint. Have you had any success there?