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.

Command LineAI & Machine LearningDeveloper ToolsAutomation & Workflows
Explore on GitHubRead Hacker News discussions
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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 1:57:11 AM 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

32 sources
boorang·Jul 26, 2026
I ran into this issue about 6 months ago when i was using mitmproxy to view the system prompts for claude code to try to diagnose degraded adherence to my CLAUDE.MD instructions: https://github.com/anthropics/claude-code/issues/18560 To summarize- they were embedding the CLAUDE.MD in a system-reminder with this disclaimer at the end: "IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task." This flew under the radar and they never addressed it, but it felt like a real part of the "nerfing" story. I no longer have a Claude Code subscription to test it, but I think it's a useful exercise for most people to sniff the traffic at least once to get an idea of what the back and forth with the Claude Code harness entails. As others have noted, Anthropic
Read the rest
seems to be on a path to make coding ever more accessible to non-coders, and in doing so has removed alot of the controls from devs who do want a more manual experience.
In The new rules of context engineering for Claude 5 generation models
boorang·Jul 26, 2026
I ran into this issue about 6 months ago when i was using mitmproxy to view the system prompts for claude code to try to diagnose degraded adherence to my CLAUDE.MD instructions: https://github.com/anthropics/claude-code/issues/18560 To summarize- they were embedding the CLAUDE.MD in a system-reminder with this disclaimer at the end: "IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task." This flew under the radar and they never addressed it, but it felt like at least a big part of the "nerfing" story. I no longer have a Claude Code subscription to test it, but I think it's a useful exercise for most people to sniff the traffic at least once to get an idea of what the back and forth with the Claude Code harness entails. As others have noted, An
Read the rest
thropic seems to be on a path to make coding ever more accessible to non-coders, and in doing so has removed alot of the controls from devs who do want a more guided experience.
In The new rules of context engineering for Claude 5 generation models
boorang·Jul 26, 2026
I spent some time running mitmproxy and watching the system prompts and it's what drove me to codex. the main issue for me was their system prompt wrapped the CLAUDE.MD with a "IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task." https://github.com/anthropics/claude-code/issues/18560 Anyhow- if anyone is sufficiently curious and has access- just tell the agent to setup an mitmproxy to watch the traffic and see what the system prompt looks like.
In The new rules of context engineering for Claude 5 generation models
boorang·Jul 24, 2026
I had to create some workarounds to avoid this bug where they include a "this might not be relevant" preamble to the CLAUDE.MD file: https://github.com/anthropics/claude-code/issues/18560 - I ended up switching to Codex and it just straight up follows the AGENTS.MD instructions, it's nice to see. This is to say, Anthropic seems to be going down the path you are describing to make the CLAUDE.MD unnecessary. But I think that's the Claude Code harness.
In Claude Cookbook
simoncion·Jul 21, 2026
> Because we continue to have zero evidence that aligment is an actual risk. I disagree. Every time one of these LLMs -say- interprets an attacker's instructions as either its system instructions or those of its user, interprets its own internal chatter as a user's command to perform a destructive operation on that user's data [0], burns all of the user's budget from getting stuck in an incredibly stupid loop, massively overbills the user because it can't reliably report which system the user is using [1], encourages a user to swap their usual cooking salt for sodium bromide, etc, etc, etc, that's a harmful alignment failure. These are real harms happening right now due to alignment failures. They're just not harms to the future of the entire species... what doomers call "existential risks", or "x-risks". You'd think that the fact that th
Read the rest
ese machines are so amazingly unreliable would be a large part of the "x-risk" conversation, but... well, it makes sense that folks like writing speculative science fiction much more than they like doing investigative reporting. [0] This general problem happens a lot, but I'm specifically thinking of that one where the Claude LLM's internal chatter lead it to believe that the task it just started was done, so it instructed the Cloud Provider to destroy the mess of "AI"-GPU-attached VMs... along with a bunch of very-expensive-to-produce data from the in-progress run. [1] <https://github.com/anthropics/claude-code/issues/73597>
In OpenAI and Hugging Face address security incident during model evaluation
marcindulak·Jul 19, 2026
Claude installer/updater had a high memory usage problem (Gigabytes of resident memory used during a fresh installation of Clade with it's native install.sh script, or during a claude update). This was reported as early as December 2025, see https://github.com/anthropics/claude-code/issues/12327#issue.... The latest Claude installer (2.1.215) possibly does not have it anymore https://github.com/anthropics/claude-code/issues/4953#issuec..., but more tries on various machines are needed to confirm that.
In Claude Code uses Bun written in Rust now

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