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

claude-code

Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.

407Distinct people
528Mentions
3Explicit recommenders
155.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.

GitHub

Where it is used

  • Pictet — “A separate team successfully implemented a disaster recovery feature with Claude Code where other AI tools had failed.” Source
  • Twilio — “Over 51 days, working solo with Claude Code, Carpenter built the Feature Factory: a self-learning development system that takes a brainstorm idea through a subagent pipeline to produce specs, tests, working code, and documentation.” Source
  • 8 more documented examples

What people are saying

My favorite is the Claude Code bugtracker, on GitHub of course: https://github.com/anthropics/claude-code/issues There is some bot that will match your issue to some other 3…

stefan_ used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

Critical Commenters criticize Anthropic for unclear billing, auto-closing bug reports, breaking features without notice, and various usability issues in Claude Code. One commenter praises the tool as the best harness on the market.

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 Anthropic for unclear billing, auto-closing bug reports, breaking features without notice, and various usability issues in Claude Code. One commenter praises the tool as the best harness on the market.

Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4 · Supporting reply 5 · 5 discussions summarized

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 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
Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files direct repository linkDebated

The discussion centers on whether Claude Code's 'Don't Ask Again' feature is at fault for leaking secrets into public repositories or if the issue stems entirely from user negligence in committing local settings files. Conversely, defenders argue that manual review is fundamentally unsustainable at scale and that the industry must shift toward automated approval or robust sandboxing despite current flaws.

429 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Showing the three threads with the most distinct people linking this repo, from 5 threads this week.

Mentions over time

HN mentions by month528 dated mentions

Observed mentions: 2025-02-24 19:48:14 UTC to 2026-10-30 14:49:33 UTC.

02550751002025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 commentsFeb 20252025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 5 mentions; 3 submissions, 2 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 13 mentions; 4 submissions, 9 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 10 mentions; 5 submissions, 5 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 15 mentions; 5 submissions, 10 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 12 mentions; 5 submissions, 7 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 21 mentions; 8 submissions, 13 commentsDec 20252026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 76 mentions; 14 submissions, 62 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 37 mentions; 9 submissions, 28 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 47 mentions; 12 submissions, 35 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 103 mentions; 29 submissions, 74 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 26 mentions; 9 submissions, 17 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 21 mentions; 4 submissions, 17 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 32 mentions; 10 submissions, 22 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 32 mentions; 12 submissions, 20 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 31 mentions; 8 submissions, 23 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 22 mentions; 4 submissions, 18 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
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC615
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC523
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC202
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC202
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC532
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC1349
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC1055
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC1019
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC15510
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC1257
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC21813
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC761462
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC37928
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC471235
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC1032974
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC26917
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC21417
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC321022
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC321220
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC31823
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC22418

What Hacker News says

528 sources
Version 2.1.313 is also missing from the official VS Code marketplace (https://marketplace.visualstudio.com/items?itemName=anthropi...). This suggest to me that it was published and pulled, which means it was Antrophic that was hacked. Version 2.1.313 is missing from the official Claude Code GitHub repo's CHANGELOG[0]. There's also no tag[1] for 2.1.313[1], but 2.1.312[2], and 2.1.314[3] exist. 0: https://github.com/anthropics/claude-code/blob/main/CHANGELO... 1: https://github.com/anthropics/claude-code/releases/tag/v2.1.... 2: https://github.com/anthropics/claude-code/releases/tag/v2.1.... 3: https://github.com/anthropics/claude-code/releases/tag/v2.1....
In Backdoor in Claude Code for VS Code extension on the Cursor Marketplace
The first backdoor I reported directly to Anthropic was on January 8, 2026. I asked Claude Code to create a public facing web app for messaging, it created an unauthenticated filedrop form and an unauthenticated web chat interface to Claude Code so anyone could send it files and tell it to execute them. This report was not hypothetical -- it was the first thing Claude did: [BUG] Claude Code Exploit: Claude Code Becomes an Unwitting Executor #45951 https://github.com/anthropics/claude-code/issues/45951
In The obscure trust looming over Anthropic's IPO
Here is an explicit example of the additional lack of coherence due to LLMs in the Anthropic Claude Code public repo itself: the human maintainer trusts LLM's incorrect understanding of the current state of code in the repo. The comment https://github.com/anthropics/claude-code/issues/30407#issue..., written by Claude Code, and posted by the human GitHub account says: > "Issues here are auto-closed by a bot when they've had no activity for a while and are missing information needed to reproduce (usually a version and steps, or a /feedback ID). Nothing is triaged solely by counting" In reality all issues in this repo are subject to time-based auto-closing, unless they collect a number of upvotes. See details at https://github.com/anthropics/claude-code/issues/87647. Therefore, I wonder whether the internal review process described in the A
Read the rest
nthropic's blog for internal repos also results in such issues, and whether Anthropic has a internal way to measure and mitigate that. The blog post says: > "When someone wants to understand a part of the codebase, they ask Claude to write an explainer for exactly that slice. It takes minutes and reflects the code as it is today." The Claude Code public repo problem shows that LLMs don't always "reflect the code as it is today", and can be a source of additional misunderstanding.
In How the Claude Code team does code review
To be clear: you can certainly do "Hi, /grill-me on X" anytime you want. You can even write "hi, /grill-me and use /search-docs", even though the /search-docs skill absolutely doesn't work. But the Claude Code _harness_ won't autoload the skill into context, so claude-the-model has to go "hmm, where can I find that skill, when I call the Skill tool with that name it no worky, so now I have to search the filesystem for that skill...". https://github.com/anthropics/claude-code/issues/92769 The <command-args> I know because I just audited my raw Claude transcripts via ccglass. You can verify by just asking Haiku "hey, /grill-me does this skill autoload for you?" and then "/grill-me hey, how many times does this text appear in your context?" You can trivially doublecheck me. The above prompts won't even eat 1% of a 5 hr on 20$ plan.
In How the Claude Code team does code review

Showing the 15 most recent of 528 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.