An unfortunate clash. I can say from experience that the sst version has a lot of issues that would benefit from more manpower, even though they are working hard. If only they could resolve their differences.
I’m definitely interested as well. This is the other side of the sst/charm ‘opencode-ai’ fork we’ve been expecting, and I can’t wait to see how they are differentiating. Talented teams on all sides, glad to see indie dev shops getting involved (guess you could include Warp or Sourcegraph here as well, though their funding models are quite different).
Crush (compared to OpenCode):
- Pro: Sexy UI with separate diff window and good information context
- Con: No SSO with Antropic. You need to generate an API key
- Con: No login with Github Copilot
- Con: Rly bad planning capabilities as agend. Acts awskwardly, executes single commands instead of batch commands.
- Con: Thus it is really slow.
- Con: Uses much more tokens for operations than OpenCode
Currently I would definately go with sst/opencode. Seems like crush is much more a beta.
One big benefit of opencode is that it lets you authenticate to GitHub Copilot. This lets you switch between all the various models Copilot supports, which is really nice.
Looks like this was the other opencode[0] and got (sensibly) rebranded:
[0]: https://github.com/opencode-ai/opencode
Exactly right. Was this one just open sourced? I don't remember seeing it when the SST opensource debacle broke. They're both under heavy development:
https://github.com/charmbracelet/crush/pulse/monthly
https://github.com/sst/opencode/pulse/monthly
An unfortunate clash. I can say from experience that the sst version has a lot of issues that would benefit from more manpower, even though they are working hard. If only they could resolve their differences.
I’m definitely interested as well. This is the other side of the sst/charm ‘opencode-ai’ fork we’ve been expecting, and I can’t wait to see how they are differentiating. Talented teams on all sides, glad to see indie dev shops getting involved (guess you could include Warp or Sourcegraph here as well, though their funding models are quite different).
Crush (compared to OpenCode): - Pro: Sexy UI with separate diff window and good information context - Con: No SSO with Antropic. You need to generate an API key - Con: No login with Github Copilot - Con: Rly bad planning capabilities as agend. Acts awskwardly, executes single commands instead of batch commands. - Con: Thus it is really slow. - Con: Uses much more tokens for operations than OpenCode
Currently I would definately go with sst/opencode. Seems like crush is much more a beta.
One big benefit of opencode is that it lets you authenticate to GitHub Copilot. This lets you switch between all the various models Copilot supports, which is really nice.
What if you don’t have a copilot plan, can you still authenticate to your GitHub account and get some free tier level services ?
https://docs.github.com/en/copilot/get-started/plans
You can get some, but model selection on free tier is smaller
1 reply →