Developers are divided between migrating to third-party harnesses like Pi for their customizability and control, versus staying with native tools like Claude Code due to concerns about stability, security, and vendor restrictions. The strongest disagreement centers on whether the flexibility of open-source harnesses outweighs the operational risks of manual configuration and potential Terms of Service violations.
493 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4anomalyco
opencode
TypeScript2025–2026
anomalyco / opencode
opencode
The open source coding agent.
129Distinct people
156Mentions
1Explicit recommenders
226.4KGitHub stars
What to know before exploring
What it is
The open source coding agent.
GitHub
Where it is used
- browser-use / browsercode (project tracking OpenCode upstream) — The browser-use/browsercode repo explicitly declares anomalyco/opencode as its upstream and documents a sync runbook; it records repeated merges and SHA ranges showing regular mechanical pulls from anomalyco/opencode into the browsercode fork. Source
What people are saying
> The recent Kimi-K2 supposedly works great. My own experience is that it is below sonnet and opus 4.0 on capability - but better than gemini 2.5 pro on tool calling. It's…
nikcub used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
Critical Commenters criticize the project for a lack of developer responsiveness to issues and cite specific security regressions in version 2. Another comment mentions legal requests associated with the repository.
A warning from this week’s discussion. Read the supporting reply
Also in these discussions
- earendil-works/pi · linked in 8 of the same discussions
- opencode-ai/opencode · linked in 4 of the same discussions
- charmbracelet/crush · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Critical
Commenters criticize the project for a lack of developer responsiveness to issues and cite specific security regressions in version 2. Another comment mentions legal requests associated with the repository.
Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · 3 discussions summarized
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.
The conversation debates the viability of LLMs in coding, contrasting arguments that they boost productivity with concerns about non-deterministic reliability and skill atrophy. Critics question the universal success claims of top programmers using AI, while others highlight the inherent unpredictability of LLM outputs as a fundamental flaw.
243 readable replies · Supporting reply 1 · Supporting reply 2Read the discussion on HN. A full-thread summary is not available yet.
Showing the three threads with the most distinct people linking this repo, from 6 threads this week.
Mentions over time
HN mentions by month156 dated mentions
Observed mentions: 2025-05-14 19:57:58 UTC to 2026-10-25 06:50:10 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| May 2025 | 2025-05-01 00:00:00 UTC | 2025-06-01 00:00:00 UTC | 1 | 1 | 0 |
| Jun 2025 | 2025-06-01 00:00:00 UTC | 2025-07-01 00:00:00 UTC | 3 | 3 | 0 |
| Jul 2025 | 2025-07-01 00:00:00 UTC | 2025-08-01 00:00:00 UTC | 15 | 2 | 13 |
| Aug 2025 | 2025-08-01 00:00:00 UTC | 2025-09-01 00:00:00 UTC | 8 | 0 | 8 |
| Sep 2025 | 2025-09-01 00:00:00 UTC | 2025-10-01 00:00:00 UTC | 1 | 0 | 1 |
| Oct 2025 | 2025-10-01 00:00:00 UTC | 2025-11-01 00:00:00 UTC | 2 | 1 | 1 |
| Nov 2025 | 2025-11-01 00:00:00 UTC | 2025-12-01 00:00:00 UTC | 6 | 0 | 6 |
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
| Jan 2026 | 2026-01-01 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 21 | 3 | 18 |
| Feb 2026 | 2026-02-01 00:00:00 UTC | 2026-03-01 00:00:00 UTC | 6 | 2 | 4 |
| Mar 2026 | 2026-03-01 00:00:00 UTC | 2026-04-01 00:00:00 UTC | 25 | 3 | 22 |
| Apr 2026 | 2026-04-01 00:00:00 UTC | 2026-05-01 00:00:00 UTC | 4 | 0 | 4 |
| May 2026 | 2026-05-01 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 5 | 1 | 4 |
| Jun 2026 | 2026-06-01 00:00:00 UTC | 2026-07-01 00:00:00 UTC | 4 | 0 | 4 |
| Jul 2026 | 2026-07-01 00:00:00 UTC | 2026-08-01 00:00:00 UTC | 11 | 1 | 10 |
| Aug 2026 | 2026-08-01 00:00:00 UTC | 2026-09-01 00:00:00 UTC | 13 | 3 | 10 |
| Sep 2026 | 2026-09-01 00:00:00 UTC | 2026-10-01 00:00:00 UTC | 3 | 1 | 2 |
| Oct 2026 | 2026-10-01 00:00:00 UTC | 2026-11-01 00:00:00 UTC | 26 | 1 | 25 |
What Hacker News says
15 sourcesTEteh_klev·Jul 31, 2025
Yes, this is that company. This is the "original":
https://github.com/sst/opencode
In Crush: Glamourous AI coding agent for your favourite terminalExactly 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.
In Crush: Glamourous AI coding agent for your favourite terminallooks cool - has anyone compared it to opencode[^1] yet?
[1]: https://github.com/sst/opencode
In Crush: Glamourous AI coding agent for your favourite terminalI recently tried Aider and it seemed a bit behind. It's not getting as much development as the others either: https://github.com/Aider-AI/aider/pulse/monthly
Compare with https://github.com/sst/opencode/pulse/monthly
In Claude Code Router> The recent Kimi-K2 supposedly works great.
My own experience is that it is below sonnet and opus 4.0 on capability - but better than gemini 2.5 pro on tool calling. It's really worth trying if you don't want to spend the $100 or $200 per month on Claude Max. I love how succinct the model is.
> you can use CC with any model via
Anthropic should just open source Claude Code - they're in a position to become the VS Code of cli coding agents.
Shout out to opencode:
https://github.com/sst/opencode
which supports all the models natively and attempts to do what CC does
In My experience with Claude Code after two weeks of adventuresThanks for the link. I'm not an emacs user and I'm more in the search of something like opencode [1], but I think it's not polished enough yet. I actually want to contribute to open source, so maybe I should create my own thing, heh.
[1]: https://github.com/sst/opencode
In AWS launches Kiro, its Cursor cloneJust make sure it's that one [1] and not the one that's attempting to confuse people over the name [2].
[1]: https://github.com/sst/opencode
[2]: https://x.com/thdxr/status/1933561254481666466
In Grok 4There’s some discussion in GitHub that suggests they are not using prompt caching, but recognize the need and are looking at it: https://github.com/sst/opencode/issues/254
In Opencode: AI coding agent, built for the terminalCome on man, the BLBG stack is where it's at! What are you using, Github Copilot?!
Seriously, though: Charm creates CLI tools, not coding agents: https://charm.sh/ https://github.com/orgs/charmbracelet/repositories
Also, https://github.com/kujtimiihoxha 's recent commits are in https://github.com/opencode-ai/opencode .
But what does https://sst.dev/ (org behind https://github.com/sst/opencode) have to do with either charm or opencode?? Like Charm, it has nothing to do with coding agents.
Not for me.
In Opencode: AI coding agent, built for the terminalClaude Code is compared in the README. https://github.com/sst/opencode?tab=readme-ov-file#how-is-th...
One other thing that would be neat to make more visible: what kind of prompts and tools are at the heart of this agent?
I found a bunch of tools here. Haven't found an overarching prompt yet. https://github.com/sst/opencode/tree/dev/packages/opencode/s...
In Opencode: AI coding agent, built for the terminalhttps://x.com/thdxr/status/1933561254481666466
ETA: The above link is at the bottom of the original submission's README. (https://github.com/sst/opencode) I posted it without context, and I have no opinion on the matter. Please read theli0nheart's comment below for an X rebuttal.
In Opencode: AI coding agent, built for the terminalOpencode: AI coding agent, built for the terminal
319 points · Open discussion