[deleted]
Crush: Glamourous AI coding agent for your favourite terminal
51–60 of 240 posts
Re: Crush: Glamourous AI coding agent for your favourite terminal
#52Re: Crush: Glamourous AI coding agent for your favourite terminal
#53Oh, it’s by Charm_!
Re: Crush: Glamourous AI coding agent for your favourite terminal
#54I don't get why terminal agents are so popular of late. Having spent more than a decade in terminal based development (vi*), and now fully moved over to a real IDE (vs code), it seems bonkers to me. The IDE is so much more... integrated
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 as it rose
Re: Crush: Glamourous AI coding agent for your favourite terminal
#55Earlier quoted context omitted.
All of the IDEs already have the AI integrations, so there's no work to do. It's not like you don't have to do the equivalent work for a TUI as an IDE for integration of a new model, it's the same config for that task. > works with no dev environment at all The terminal is a dev environment, my IDE has it built in. Copilot can read both the terminal and the files in my project, it even opens them and shows me the dif…
The words "the AI integrations" are doing some weird work there, right? Agents all have opinionated structure, which changes how effective they are at working on different kinds of problems.
By AI (model) integrations, it's mostly pointing at a URL and what name the API keys are under in ENV. Everyone has pretty much adopted MCP for agents at this point, so also very standardized integration there too
Re: Crush: Glamourous AI coding agent for your favourite terminal
#56Earlier 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…
LM Studio is probably better in this regard. I was able to get LM studio to work with Cursor, a product known to specifically avoid giving support to local models. The only requirement is if it uses servers as a middle-man, which is what Cursor does, you need to port forward.
Re: Crush: Glamourous AI coding agent for your favourite terminal
#57I don't get why terminal agents are so popular of late. Having spent more than a decade in terminal based development (vi*), and now fully moved over to a real IDE (vs code), it seems bonkers to me. The IDE is so much more... integrated
> a real IDE (vs code) Much better to use Neovim than a very clunky slow editor like VS Code or Jetbrains just to edit a text file. The keyboard is far faster than clicking everywhere with the mouse.
I use the Vim plugin to keep my keyboard navigation, editor modes, and such... best of both worlds.
I think the sentiment that VS Code is clunky and slow is outdated. I have seen no noticeable impact since moving over from neovim
Re: Crush: Glamourous AI coding agent for your favourite terminal
#58I don't get why terminal agents are so popular of late. Having spent more than a decade in terminal based development (vi*), and now fully moved over to a real IDE (vs code), it seems bonkers to me. The IDE is so much more... integrated
Not new to AI agents, either. I'm sure you can set up vim to be like an IDE, but unless you're coding over ssh, I don't know why it's preferable to an actual IDE (even one with vim bindings). GUIs are just better for many things. If the optimal way to do a particular thing is a grid of rectangular characters with no mouse input, nothing prevents you having one of those in your GUI where it makes sense. For instance,…
I primarily code over ssh with VS Code Remote to cloud vm instances
Re: Crush: Glamourous AI coding agent for your favourite terminal
#59I 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 node.js, so I guess there's some chance that the terminal output is optimized to minimize large redraws?).
So they just don't tend to work at all like you'd expect a REPL or a CLI to work, despite having exactly the same interaction model of executing command prompts. But they also don't feel at all like fullscreen Unix TUIs normally would, whether we're talking editors or reader programs (mail readers, news readers, browsers).
Is this just all the new entrants copying Claude Code, or did this trend get started even earlier than that? (This is one of the reasons Aider is still my go-to; it looks and feels the way a REPL is supposed to.)
Re: Crush: Glamourous AI coding agent for your favourite terminal
#60I don't get why terminal agents are so popular of late. Having spent more than a decade in terminal based development (vi*), and now fully moved over to a real IDE (vs code), it seems bonkers to me. The IDE is so much more... integrated
I also use IDEs and I think people who use terminal-based editors are lunatics but I prefer terminal-based coding agents (I don't use them a lot to be fair). It's easier to see the diff file by file and really control what the AI does IMO. On another note VS Code is not an IDE, it's a text editor.
Copilot opens the files and shows me the diff, that is not missing in the IDE
Perhaps your definition of IDE is more restrictive. I see VS Code as my environment where I develop with masses of integrations