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, 3:30:57 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
smartbit·Aug 31, 2026
According to https://gist.github.com/unkn0wncode/f87295d055dd0f0e8082358a... among many, the environment variable CLAUDE_CODE_SUPPRESS_SESSION_ATTRIBUTION was added in CC version 2.1.202 on July 8, 2026. Setting it to value 1 will suppresses session-URL attribution (returns null instead of the session attribution info). I will set it, as suggested in this July 18 comment https://github.com/anthropics/claude-code/issues/66504#issue... And in ~/.claude/CLAUDE.md this 'git rule' which works fine: Never add a Co-Authored-By line or any other reference to Claude in commit messages.
In Claude Session URL appended to commit messages and PR descriptions by default
MuffinFlavored·Aug 22, 2026
I submitted an application for Anthropic's Cyber Verification Program. I was approved. 3 months later, my approval was degraded into "in review" (revoked). I'm sure my account was flagged based on contents of debugging/researching firmwares/etc. I opened a support ticket. No response. I opened another support ticket. No response. 1-2 weeks later, I got a response that I will not be re-approved and I need to reapply. No problem. The page to reapply on does not allow me to re-apply because it my account is stuck in an "in review" status. https://github.com/anthropics/claude-code/issues/84352 The community thinks it's a bug. I'm 95% sure it's not and a bunch of us who were previously approved had it revoked due to flagged content and will not be reapproved. I switched to Codex + got TAC approved instantly and have not looked back. It's a sha
Read the rest
me. That's 100% separate from whatever the heck the quality of Opus 5's outputs are. The way it talks... insane. I would bet a good amount of money their next release will focus "reduced simplified responses" if I had to guess. $2t company by the way
In Anthropic appears to be A/B testing reduced effort levels in Claude Code
deaux·Aug 20, 2026
What's interesting is that the closure event was mysteriously deleted [0]. Compare with others like [1] which do keep the "bcherny closed this as completed 1m ago"; for some reason it's missing here, even though Boris closed it as completed in the same manner as confirmed by GitHub notifications. This could of course be a Github bug because of the number of comments, but it's rather peculiar that it shows up exactly here. Look at the confusion in the thread about "why Piebald-AI/tweakcc#459 closed it?". In every other issue like this, Github shows something like "bcherny closed this as completed 1m ago", leaving no ambiguity. Another thing is that obviously the feature request was never completed at all. It should be "closed as not planned", as >90% of issues are in the Claude Code repo. Yet just for this one they make an exception and cl
Read the rest
ose it as "completed", breaking precedent. It's so chickenshit. Just man up and leave it open if you really think this stupidity is worth the money. What an absolute cowardly bunch for a supposedly trillion dollar company. [0] https://github.com/anthropics/claude-code/issues/6235#event-... [1] https://github.com/anthropics/claude-code/issues/66955#event...
In Feature Request: Support AGENTS.md

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.