The 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.
Aider says they do, but I haven’t tried it.
Crush: Glamourous AI coding agent for your favourite terminal
121–130 of 240 posts
Re: Crush: Glamourous AI coding agent for your favourite terminal
#122The 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.
Crush has an open issue (2 weeks) to add Ollama support - it's in progress.
They should add "custom endpoint" support instead [0].
Re: Crush: Glamourous AI coding agent for your favourite terminal
#123Someone please make/release a Rust CLI. OpenAI what are you doing with Codex?
Re: Crush: Glamourous AI coding agent for your favourite terminal
#124I would love a comparison between all these new tools, like this with Claude Code, opencode, aider and cortex. I just can’t get an easy overview of how each tool works and is different
This used to be opencode but was renamed after some fallout between the devs I think.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#125I would love a comparison between all these new tools, like this with Claude Code, opencode, aider and cortex. I just can’t get an easy overview of how each tool works and is different
The performance not only depends on the tool, it also depends on the model, and the codebase you are working on (context), and the task given (prompt).
And all these factors are not independent. Some combinations work better than others. For example:
- Claude Sonnet 4 might work well with feature implementation, on backend code python code using Claude Code.
- Gemini 2.5 Pro works better for big fixes on frontend react codebases.
...
So you can't just test the tools alone and keep everything else constant. Instead you get a combinatorial explosion of tool * model * context * prompt to test.
16x Eval can tackle parts of the problem, but it doesn't cover factors like tools yet.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#126Re: Crush: Glamourous AI coding agent for your favourite terminal
#127Earlier quoted context omitted.
For me, the workflow that Claude Code provides via VSCode plugins or even IntelliJ integration is great. TUI for talking to the agent and then some mild GUI gloss around diffs and such. I like terminal things because they are easy to use in context wherever I need them - whether that's in my shell locally or over SSH, or in the integrated terminal in whatever IDE I happen to be using. I use vim if I need to make a qu…
My VS Code has a terminal and can remote into any machine and edit code / terminal there. What I don't get is going back to terminal first approaches and why so many companies are putting these out (except that it is probably (1) easy to build (2) everyone is doing it hype cycle). It was similar when everyone was building ChatGPT functions or whatever before MCP came out. I expect the TUI cycle will fade as quickly a…
I think a fairly large number of people using IDEs use them for the writing code coding part almost exclusively, e.g. don't use many/any of the other "integrated" features like VCS integration, build integration, etc. As an example, I think most people I've seen use vscode still use git via the cli (less sure but I'd guess most of them use a separate terminal even).
I don't know for sure or have anything besides anecdotal evidence but I'd wager this is a majority of vscode users.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#128I 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…
What bothers me is that what I like about terminals is the scrolling workflow of writing commands and seeing my actions and outputs from various sources and programs sequentially in a log. So what I want is a rich full-HTML multi-program scrolling workflow. Instead, people are combining the worst of both worlds. What are they doing? Give me superior UI in a superior rendering system, not inferior UI in an inferior rendering system, god damn it.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#129Re: Crush: Glamourous AI coding agent for your favourite terminal
#130Played with it a bit. So far it lacks some key functionality for my use case: I need to be able to launch an interactive session with a prefilled prompt. I like to spawn tmux sessions running an agent with a prompt in a single command, and then check in on it later if any followup prompting is needed.
Other papercuts: no up/down history, and the "open editor" command appears to do nothing.
Still, it's a _ridiculously_ pretty app. 5 stars. Would that all TUIs were this pleasing to look at.