by autocracy101
9 subcomments
- Author here. I built this in a few hours after the Claude Code leak.
I've been working on my own coding agent setup for a while. I mostly use pi [0] because it's minimal and easy to extend. When the leak happened, I wanted to study how Anthropic structured things: the tool system, how the agent loop flows, A 500K line codebase is a lot to navigate, so I mapped it visually to give myself a quick reference I could come back to while adapting ideas into my own harness and workflow.
I'm actively updating the site based on feedback from this thread. If anything looks off, or you find something I missed, lmk.
[0] https://pi.dev/
by amangsingh
24 subcomments
- A 500k line codebase for an agent CLI proves one thing: making a probabilistic LLM behave deterministically is a massive state-management nightmare. Right now, they're great for prompting simple sites/platforms but they break at large enterprise repos.
If you don't have a rigid, external state machine governing the workflow, you have to brute-force reliability. That codebase bloat is likely 90% defensive programming; frustration regexes, context sanitizers, tool-retry loops, and state rollbacks just to stop the agent from drifting or silently breaking things.
The visual map is great, but from an architectural perspective, we're still herding cats with massive code volume instead of actually governing the agents at the system level.
by throwatdem12311
6 subcomments
- I know it seems counter-intuitive but are there any agent harnesses that aren’t written with AI? All these half a million LoC codebases seem insane to me when I run my business on a full-stack web application that’s like 50k lines of code and my MvP was like 10k. These are just TUIs that call a model endpoint with some shell-out commands. These things have only been around in time measured in months, half a million LoC is crazy to me.
by Andebugulin
2 subcomments
- If it was 2020, it would be hard to imagine that after some hours/days you getting a visual representation of the leak with such detailed stats lol
by ernst_klim
5 subcomments
- > 500k lines of code
Isn't it a simple REPL with some tools and integrations, written in a very high level language? How the hell is it so big? Is it because it's vibecoded and LLMs strive for bloat, or is it meaningful complexity?
- Even today, I'm still astounded that there are people capable of building a gorgeous and interesting site like this in less than 2 days...
by stingraycharles
4 subcomments
- I guess they really do eat their own dogfood and vibe code their way through it without care for technical debt? In a way, it’s a good challenge, but it’s fairly painful to watch the current state of the project (which is about a year old now, so it should be in prime shape).
- Here's a codeberg repo with the leaked source: https://codeberg.org/wklm/claude-code
- Dang! Glad to see others doing this. I totally made this site yesterday like 11 hours ago :/ but did not get the traction.
I love your implementation.
Here was my first stab:
https://news.ycombinator.com/item?id=47595140
https://brandonrc.github.io/journey-through-claude-code/
- I'm developing an agent focused on A2A, support for small models, and privacy (https://swival.dev).
I looked at the leaked code expecting some "secret sauce", but honestly didn't found anything interesting.
I don't get the hype around Claude Code. There's nothing new or unique. The real strength are the models.
- Feel free to add this to Awesome Claude code. https://github.com/rosaboyle/awesome-cc-oss
- Appreciate the effort, but this is very basic and nothing you need the source code to understand. I was expecting a deep dive into what specific decisions they made, but not how an loop of tool calls works
- I built a site that lets you explore and browse all the Claude Code prompts in a structured way:
https://ccprompts.info
by restlessforge
2 subcomments
- Okay those "hidden features" are amazing, especially the cross-session referencing. I hope we can look forward to that in the future
Also I definitely want a Claude Code spirit animal
- The KAIROS persistent agent mode is the most significant finding — autonomous background tasks in a black box nobody knew about. This is why local open-weight models are gaining traction. Run inference on-device (like aiME on iOS/Android) and you know exactly what's happening with your data.
Website : https://coticsy.com/aime.html
iOS: https://apps.apple.com/us/app/aime-ondevice-ai/id6754805828
Android: https://play.google.com/store/apps/details?id=com.coticsy.ll...
- There's this weird thing about AI generated content where it has the perfect presentation but conveys very little.
For example the whole animation on this website, what does it say beyond that you make a request to backend and get a response that may have some tool call?
- > also related: https://www.ccleaks.com
This deployment is temporarily paused
by psychomfa_tiger
0 subcomment
- The tool system breakdown is useful. I've been running Claude Code daily for a few months and some things in there explain behaviors I noticed but couldn't figure out. Like why sometimes it re-reads files it already read 30 seconds ago. Makes more sense now seeing how the context window management works internally, it's being more conservative about what it assumes is still accurate. The permission gate flow is the part I care about most. When I'm away from my machine and the agent hits a permission prompt, that's where my workflow falls apart. Knowing how it structures those requests internally is helpful for anyone building tooling around it. One thing the guide doesn't cover much is how sessions are meant to be resumed. The checkpoint system is interesting but in practice I find session resume pretty fragile once you go past a certain context length.
- I've been building a multi-agent pipeline on top of Claude Code — 7 agents chained together (scout, researcher, writer, editor, evaluator, publisher). One surprising lesson: the Editor agent approved 100% of articles while the independent Evaluator rejected 45%. LLMs are bad at being critical of LLM
output. We ended up enforcing title quality with regex instead of prompts because the Writer kept ignoring banned-word rules.
by sibtain1997
1 subcomments
- Kairos and auto-dream are more interesting than anything in the agent loop section. Memory consolidation between sessions is the actual unsolved problem. The rest is just plumbing tbh
- I've been using Claude Code heavily for the last few weeks building out a multi-agent system, and the token economics caught me off guard — I hit 75% of my Pro weekly budget faster than expected. I don't code myself, so Claude Code handles all the actual implementation work.
What I've learned about cost management: the real decision isn't "should I code this myself or use Claude Code" — it's "should I spawn Claude Code or handle this through a different approach entirely?" For complex builds where I need something architected from scratch, Claude Code is worth it. For smaller tasks or iteration on existing code, I've started using Sonnet in the web interface with the file as context instead. The visual guide here is helpful because it shows you what Claude Code is actually doing under the hood — understanding that workflow helps you predict whether a task will be a quick fix or a deep exploration that burns through your budget.
- Thanks to Claude Code, we got such a beautifully polished and dazzling website that gives a complete introduction to itself the very moment the leak happened :)
- Hello everyone! It's me behind the website.
I launched the site minutes after the leak, obviously vibecoded it.
Kept working on it day and night to fix all the issues.
I was using vercel free plan and did not expect this huge response. The site went down when I took a nap of 3 hours.
Woke up with calls from my team for a meeting. Saw the msgs of people telling me site is down.
Fixed the issue.
And now, I am updating it on regular speed.
Thank you for all the positive and negative feedback, Will consider it all in my future projects.
- Pardon me, but I think it's rather obvious that it worked this way?
The real value of Anthropic is in the models that they spent hundreds of millions training. Anyone can build a frontend that does a loop, using the model to call tools and accomplish a task. People do it every day.
Sure, they've worked hard to perfect this particular frontend. But it's not like any of this is revolutionary.
by JoostBoer
2 subcomments
- I have no engineering background. I build websites and tools for a living. Claude Code changed what's possible for me in a way that's hard to overstate.
I can't evaluate the source code architecture. What I can say is that before this, I had ideas I couldn't execute without hiring a developer. Now I ship them myself. Not prototypes, not demos. Real products that people use and pay for.
The leaked internals are interesting to engineers. From where I sit, the interesting part is that it works well enough that someone without a CS degree can build production software with it. That's the actual story.
- The interesting thing about agent tool use is how binary it is. The agent either calls the tool or doesn't. The harder problem is social agency, where the AI has to decide whether to participate at all. We built a pre-filter for this (cheap model reads the room before the expensive model runs) and the failure modes are fascinating. The model would reason correctly in its chain-of-thought, 'this person is left hanging, I should respond' and then output the opposite boolean. Turned out Haiku has a systematic false-bias on boolean tool outputs. Had to invert the schema
by techpression
0 subcomment
- 519K lines of code for something that is using the baseline *nix tools for pretty much everything important, how do they even manage to bloat it this much? I mean I know how technically, but it's still depressing.
Can't they ask CC to make it good, instead of asking it to make it bigger?
- Is it just me or do I not find the Claude Code application that fascinating?
I use it all day and love it. Don't get me wrong. But it's a terminal-based app that talks to an LLM and calls local functions. Ooookay…
by brandensilva
0 subcomment
- ccleaks.com seems to be "temporarily paused" from Vercel.
Here is another one that goes in depth as well: www.markdown.engineering for anyone going deep on learning.
by vivzkestrel
1 subcomments
- would be nice if the transformers code for one of these frontier LLM models got leaked, HN will have a field day with a reveal like that
- This is AI slop.
First command I looked at:
/stickers:
Displays earned achievement stickers for milestones like first commit, 100 tool calls, or marathon sessions. Stickers are stored in the user profile and rendered as ASCII art in the terminal.
That is not what it does at all - it takes you to a stickermule website.What is the motivation for someone to put out junk like this?
- This tool is useful if you want to see all the internal commands claude agents are making in real-time:
https://github.com/simple10/agents-observe
- Nice job - I'm a fan. Makes it easy to get the big picture so I know where to dive in.
- I like the Claude desktop interface. The color scheme, presentation, fonts, etc. Is there a CSS I can find for the desktop version - I assume it's using some kind of web rendering engine and CSS is part of it.
by samuelknight
0 subcomment
- On the one hand I don't understand why it needs to be half a million lines. However code is becoming machine shaped so the maintenance bloat of titanic amounts of code and state are actually shrinking.
- I don't know why people obsess and spend so much time on this codebase. It isn't (and never was)alien technology. It's just mediocre typescript generated by an LLM
- Really nice visualisation of this, makes understanding the flow at a high levle pretty clear. Also the tool system and command catalog, particularly the gated ones are super interesting.
by MattCruikshank
0 subcomment
- Don't do the "noise" thing this web page does. It hurts my eyes so bad. Why would you purposefully make your page look like a low-quality JPG?
by pandemik09
0 subcomment
- To me the question isn’t “why is the codebase so large,” it’s “why is the model still being asked to do orchestration at all.”
by tallesborges92
0 subcomment
- Please share the prompt/skills used to build it
by simonreiff
0 subcomment
- Nice site. I might suggest moving SendMessage to the Hidden Features as they don't appear to have implemented a ReadMessage or ListMessages tools.
- I mean, I get it: vibe-coded software deserves vibe-coded coverage. But I would at least appreciate it if the main part of it, the animation, went at a speed that at least makes it possible to follow along and didn't glitch out with elements randomly disappearing in Firefox...
How is this on the front page?
- Has anyone tried USER_TYPE "ant"? I might be crazy, but I have not hit my limit yet after 3 questions.
- I hope /Buddy is ported across to OpenCode.
- I'm just admiring the visualizations this guy built in under a day. Wondering how he did it so fast
- Btw, the 500K is just the source - it does not include tests. I would imagine there are at least 2-4x tests.
by shuntaka9576
0 subcomment
- A year ago I wouldn't have guessed a TUI could be a competitive advantage. But "harness engineering" became a thing, and it turns out the agent wrapper — tool orchestration, context management, permission flows — is where real product value lives. Not as much as the models themselves, but more than most people expected. This leak is a painful reminder of that.
by RishabhGarg12
0 subcomment
- This is funny because this looks exactly like my vibe coded Portfolio - colors and all.
- So it does use ripgrep and not unix grep. [0] I knew it from some other commenters here on HN, but it's nice to see it in the source as well.
0 - https://github.com/zackautocracy/claude-code/blob/main/src/u...
- I think this is unethical, and "everyone else is also doing it" is not a valid excuse.
- However, excellent development practices involve modularizing code based on functional domains or responsibilities.
The utils directory should only contain truly generic, business-agnostic utilities (such as date retrieval, simple string manipulation, etc.).
We can see that the code produced by Vibe is not what a professional engineer would write. This may be due to the engineers using the Vibe tool.
by sourcecodeplz
0 subcomment
- Nice presentation. The reality is there is nothing really special about the claude code harness?
- Ah, good well-architected code, finally... With most of the code in utils/other :D
by delphic-frog
0 subcomment
- Looks like ccleaks is down eek - not long before ccunpacked has same fate.
by sscaryterry
0 subcomment
- No point in reading this, they are continuing to lobotomize it daily...
- FYI - This pops at my work as a sec threat via Cisco Umbrella. :D
- Source leak or free code review? I can say that there is no bad publicity.
- I prefer this mapping from Nikita @ CosmoGraph: https://run.cosmograph.app/public/dfb673fc-bdb9-4713-a6d6-20...
- why do people care so much? it's just an agentic loop
- what is so fascinating about claude code. we have codex that is open source already. is there something special to learn from claude code?
by bilalbayram
0 subcomment
- Same guide for opencode would be nice too
- You guys all get it’s an April joke?
- No mention of undercover mode?
- I expect dozens more "research articles" that
- find nothing
- still manage to fill entire lages
- somehow have a similar structure
- are boring as fuck
At least this one is 3/4, the previous one had BINGO.
by mdavid626
2 subcomments
- How the hell is it 500k lines?
- I got a goose
War flashbacks to genshin
by Hannah_Adam
0 subcomment
- Is that safe to use?
by Vektorceraptor
0 subcomment
- Hey, nice job! Next time tell calude to add some explosions, car crashes and stuntment into the design! Who cares about content anyway ...
https://speculumx.at/blogpost/getting-sick-of-ai-slop
by blueTiger33
0 subcomment
- its April fools joke. this has really gone wide
- nice example: Find all TODO
spin the AI machine
i do shift ctrl F
by fartfeatures
0 subcomment
- Ccleaks is down?
by inside_story
0 subcomment
- cool Archaeologization Collection Output
- nice
- Now we just let the AI "move fast and break things".
by phplovesong
0 subcomment
- Holy fukking hell thats some bad code. Full blown AI slop.
by steveharing1
0 subcomment
- Anthropic is now more open than OpenAI Itself lmao!
- this claude code leak is such a fuck up...
The fact that now every agent designer knows what was already built is a huge shot of steroids to their codebase!
by jruohonen
2 subcomments
- Thanks, I'll use this for teaching next week (on what not to do). BashTool.ts :D But, in general, I guess it just shows yet again that the emperor has no clothes.
- [dead]
by techpulselab
0 subcomment
- [flagged]
- [dead]
by Adam_cipher
0 subcomment
- [dead]
- [dead]
- [dead]
by AIOperator2026
0 subcomment
- [dead]
- [dead]
- [dead]
- [dead]
by panavinsingh
0 subcomment
- [dead]
- [flagged]
- [dead]
- [dead]
- [dead]
- [dead]
- [dead]
by hahhhha500012
0 subcomment
- [dead]
by T3RMINATED
0 subcomment
- [dead]
- [flagged]
- [flagged]
by sscaryterry
1 subcomments
- Enshitification galore