I'm so confused by this. I saw this post on HN, and then ended up installing the opencode-ai/opencode one via homebrew somehow (I guess I did a google search and ended up on the wrong github). But then sst/opencode is the one that links to the website opencode.ai and I was reading the docs on that website. Which one is better?
Isn't it more appropriate to compare this to aider?
I prefer the command line tools to IDE integration, even though I don't feel like the contextual options are great. In other words, I don't always feel that I can see the changes fully. I like Claude Code's option to expand the result using ctrl-r, and I like the diffs it provides. But, it still feels like there is a way to get better than what I see inside Zed and what I see inside Claude and Aider.
Maybe an editor that can be controlled and modified on the fly using natural language?
Just wanted to say I had been happily plodding along using AI tools in Zed, which had worked pretty well but seeing the SST team was behind OpenCode I decided to finally give a terminal based agent a try. I was blown away, primarily by the feedback loops of say OpenCode writing new tests, running the test suite, seeing the tests errored and looping back start the whole process again. That looping does not happen in Zed!
It was the first time I felt like I could write up a large prompt, walk away from my laptop, and come back to a lot of work having been done. I've been super happy with the experience so far.
I feel like the guy behind this project loves getting into internet fights to create drama/clickbait. That being said, it's a cool project - still in its early stages and nowhere as usable as the other CLIs...but it's a darn shame about all the drama.
I am using Claude Code almost exclusively. I am using the Claude Pro subscription and it allows Claude Code usage, with limits on the number of prompts per 5 hours, according to their site. I have not hit these limits yet even though I use this full-time, daily.
With other tools, do I have to pay API based costs or are there ways to use my subscription? As I see it, the API costs add up quickly. That means we can be stuck with a few tools from the top tier model companies.
Terminal UIs is such a step backward. It's only attractive to people who have a preexisting emotional attachment to the terminal.
I should be one of those people, I guess. I love shell scripts and all the rest... but interactive terminal UIs have always sucked.
So much of what AI companies are putting out is designed to capture developer mindshare. Substantive improvements to their core product (models) are few and far between, so they release these fidgets about once a month to keep the hope alive.
From that standpoint, TUI makes sense because it obscures the process and the result enough to sucker more people into the vibe-coding money hole.
Been spending the day with this. I have no experience with TUI tools like Claude Code, so I had no expectations going into it. My first go with it was unfortunately soured by a broken /init command, but that actually got fixed almost immediately -- the Discord is fairly busy. That one hitch aside, I authed it into my Github Copilot account and immediately I was able to start vibing out, adding some features to a random project of mine. Worked great.
I'm gonna stick with this for now. The dev is responsive, updates regularly, it works fine, and it just seems to keep getting better.
25 comments
[ 2.9 ms ] story [ 40.7 ms ] threadI prefer the command line tools to IDE integration, even though I don't feel like the contextual options are great. In other words, I don't always feel that I can see the changes fully. I like Claude Code's option to expand the result using ctrl-r, and I like the diffs it provides. But, it still feels like there is a way to get better than what I see inside Zed and what I see inside Claude and Aider.
Maybe an editor that can be controlled and modified on the fly using natural language?
other than the focus on tui design, does this have any advantage over Claude Code, Aider, Gemini using the same model?
we're a little over a month into development and have a lot on our roadmap
the cli is client/server model - the TUI is our initial focus but the goal is to build alternative frontends, mobile, web, desktop, etc
we think of our task as building a very good code review tool - you'll see more of that side in the following weeks
can answer any questions here
It was the first time I felt like I could write up a large prompt, walk away from my laptop, and come back to a lot of work having been done. I've been super happy with the experience so far.
I am using Claude Code almost exclusively. I am using the Claude Pro subscription and it allows Claude Code usage, with limits on the number of prompts per 5 hours, according to their site. I have not hit these limits yet even though I use this full-time, daily.
With other tools, do I have to pay API based costs or are there ways to use my subscription? As I see it, the API costs add up quickly. That means we can be stuck with a few tools from the top tier model companies.
I'm curious about how they feel to use and their "performance".
I should be one of those people, I guess. I love shell scripts and all the rest... but interactive terminal UIs have always sucked.
So much of what AI companies are putting out is designed to capture developer mindshare. Substantive improvements to their core product (models) are few and far between, so they release these fidgets about once a month to keep the hope alive.
From that standpoint, TUI makes sense because it obscures the process and the result enough to sucker more people into the vibe-coding money hole.
I'm gonna stick with this for now. The dev is responsive, updates regularly, it works fine, and it just seems to keep getting better.