HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
anomalyco
opencode
TypeScript2025–2026
anomalyco / opencode

opencode

The open source coding agent.

129Distinct people
156Mentions
1Explicit recommenders
226.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The open source coding agent.

GitHub

Where it is used

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

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.

Goodbye Claude, hello Pi direct repository linkDebated

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 4
Why I will not be using LLMs in my coding direct repository linkDebated

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 2

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.

01020302025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 20252025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 15 mentions; 2 submissions, 13 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 21 mentions; 3 submissions, 18 commentsJan 20262026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 25 mentions; 3 submissions, 22 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 13 mentions; 3 submissions, 10 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 26 mentions; 1 submissions, 25 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC110
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC330
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC15213
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC808
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC101
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC211
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC606
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC21318
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC624
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC25322
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC404
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC514
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC404
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC11110
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC13310
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC312
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC26125

What Hacker News says

21 sources
I built Wiz because I was tired of context-switching between remembering tool syntax and actually doing security work. ## Background I've been doing security assessments for a while, and the workflow is always: 1. Remember the right tool for the job 2. Look up the flags (again) 3. Run the command 4. Parse the output manually 5. Copy findings to a spreadsheet 6. Repeat 100 times 7. Manually write the report ## What Wiz Does Wiz lets you describe what you want in natural language: "check if this Apache server is vulnerable to path traversal" And it: 1. Selects the right tools (nuclei with CVE-2021-41773 templates) 2. Runs them with correct parameters 3. Parses the output into structured findings 4. Classifies by severity (Critical/High/Medium/Low) 5. Stores with evidence for the report 6. Generates professional reports when you're done ## T
Read the rest
echnical Details Built on OpenCode (https://github.com/sst/opencode), which provides: - Superior agent architecture vs generic LLM CLIs - Extensible tool framework with typed I/O - Multi-LLM support (Claude, GPT-4, Gemini, local models) Wiz adds a security layer: - 30+ tool integrations with output parsers - Findings database with OWASP/CVE categorization - Governance engine (scope enforcement, audit trails) - Report generation (HTML, PDF, Markdown) ## What It's NOT - Not a replacement for knowing what you're doing - Not for unauthorized testing - Not a magic "hack anything" button It's an assistant that handles the tedious parts so you can focus on analysis. ## Stack - TypeScript/Bun - Runs on Kali, Parrot, any Linux, macOS, Windows - Requires API key (Claude recommended, GPT-4 works too) ## Links - GitHub: https://github.com/code3hr/opencode - Downloads: https://github.com/code3hr/opencode/releases/latest Open source, MIT licensed. Feedback welcome! ``` --- ## Quick Demo Script (for Video/GIF) ``` # Terminal recording script $ ./cyxwiz > scan 10.0.0.5 for vulnerabilities [Wiz runs nmap, detects Apache 2.4.41] [Wiz runs nikto, finds misconfigurations] [Wiz runs nuclei, matches CVE-2021-41773] Found 1 critical, 2 high, 3 medium findings. > show critical findings CRITICAL: CVE-2021-41773 - Apache Path Traversal - Target: 10.0.0.5:80 - Impact: Remote Code Execution - Evidence: [response data] - Remediation: Upgrade to Apache 2.4.51+ > generate report Report generated: assessment-2024-01-15.html ```
In Wiz – AI-Powered Pentest Assistant (Open Source)
csressel·Jan 14, 2026Submission

Show HN: Nori CLI, a better interface for Claude Code (no flicker)

Hi HN, my name's Clifford and I'm one of the creators of Nori. I’ve been using Claude Code heavily since last summer, and after understanding some of the tradeoffs with their TUI implementation, I knew I couldn't see myself living for years with this interface as one of my daily-driver tools. It is not a hard problem to make monospace text output performant, so why does Claude Code suffer from flicker and strobing in the terminal (https://github.com/anthropics/claude-code/issues/1913)? Even after they've released multiple improvements for this, I still see the issue in terminal splits with fewer rows, or in less performant emulators, and even within a virtual TTY (the absolute simplest environment to run an interactive program in). After digging in throughout the past half year, the issue is mostly inevitable because Claude reprints full
Read the rest
terminal history without using alt screen mode and uses a React-based framework (Ink) to render and style their text. That's great for JS+CSS being "on distribution" for LLMs in order to vibecode the continued development of Claude Code, but it doesn't deliver the experience I'd like. The frameworks they've chosen also have limitations around [terminal input parsing (i.e. the shift enter issues from last year: https://github.com/anomalyco/opencode/issues/1505#issuecomme...). Great terminal interfaces I've lived with for years (neovim, btop, helix, Cataclysm DDA, etc) don't sacrifice user experience as a tradeoff for development convenience. They build resilient terminal interfaces on languages more appropriate for this problem, like C or C++ or Rust. Finally, while I'm definitely rooting for Anthropic to continue improving their products, I can't see myself coupling a commandline tool I use often with a single LLM provider. It would be insane if pushing my code to GitHub required me to edit it in VSCode — I want my tooling to do one thing well, and that's display the read-eval-tool-loop from talking to an agent. Opus 4.5 has been stellar, but it's nonnegotiable to me that I can try out varied providers with the same tools I plan to use everyday. Claude Code will not be working long term on how best to interface with multiple agents, from varying providers, in one terminal pane, and that makes perfect sense for their business. However based on our other experiences building out profiles and skillsets for agents, deeper customizations of agent instructions and subagents, and parallel worktrees for local agents, we have a lot of vision for how to handle local agentic work. And with the current design to integrate at the agent-level, we don't plan on working around the OAuth flows or spoofing the system prompt outside of the Claude Code SDK (like with the OpenCode situation), and risk the tools coming into conflict with the providers. These were the main considerations that went into designing Nori CLI. It's a very thin and very fast TUI wrapper around multiple agent providers. It integrates with providers at the agent level, instead of the model level. Not only does that provide better performance in our experience, but that is also *compliant with current ToS for subscription based usage.* This is a very early version, but given the timing this week it might give you a flicker-free way to code with Claude Code! The project is open source, and built on the stellar work by folks at Zed (on the abstraction over varied coding agents), and the folks working on Codex CLI (who have put together one of the nicest proprietary terminal experiences). I'm very curious: What are the Claude Code features you couldn't give up, to make the switch to a tool like this? What are the Claude Code features that work as intended, but you can't stand?
37 points · Open discussion
Seems `session/:id/shell` was also `session/:id/bash` and originally `session/:id/command` in some commits. Maybe I'm using GitHub code search wrongly, but it appears this was just never part of even a pull request - the practice of just having someone pushing to `dev` (default branch) which then will be tagged should perhaps also be revisited. (Several more commits under `wip: bash` and `feat: bash commands`) https://github.com/anomalyco/opencode/commit/7505fa61b9caa17... https://github.com/anomalyco/opencode/commit/93b71477e665600...
In Unauthenticated remote code execution in OpenCode
The fix has been merged in https://github.com/anomalyco/opencode-anthropic-auth/pull/11, and PR https://github.com/anomalyco/opencode/pull/7432 is open to bump the version. Until it's released, here's a workaround: 1. git clone https://github.com/anomalyco/opencode-anthropic-auth.git 2. Add to ~/.config/opencode/opencode.json: "plugin": ["file:///path/to/opencode-anthropic-auth/index.mjs"] 3. Run: OPENCODE_DISABLE_DEFAULT_PLUGINS=true opencode
In Anthropic blocks third-party use of Claude Code subscriptions
For folks not following the drama: Anthropic's $200/month subscription for Claude Code is much cheaper than Anthropic's pay-as-you-go API. In a month of Claude Code, it's easy to use so many LLM tokens that it would have cost you more than $1,000 if you'd paid via the API. Why is Anthropic offering such favorable pricing to subscribers? I dunno. But they really want you to use the Claude Code™ CLI with that subscription, not the open-source OpenCode CLI. They want OpenCode users to pay API prices, which could be 5x or more. So, of course, OpenCode has implemented a workaround, so that folks paying "only" $200/month can use their preferred OpenCode CLI at Anthropic's all-you-can-eat token buffet. https://github.com/anomalyco/opencode/issues/7410#issuecomme... Everything about this is ridiculous, and it's all Anthropic's fault. Anthropic sh
Read the rest
ouldn't have an all-you-can-eat plan for $200 when their pay-as-you-go plan would cost more than $1,000+ for comparable usage. Their subscription plans should just sell you API credits at, like, 20% off. More importantly, Anthropic should have open sourced their Claude Code CLI a year ago. (They can and should just open source it now.)
In Anthropic blocks third-party use of Claude Code subscriptions

Showing the 15 most recent of 21 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.