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.
Claude Code Unpacked : A visual guide
141–150 of 464 posts
Re: Claude Code Unpacked : A visual guide
#142Author 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…
This is nice, I really like the style/tone/cadence.
The only suggestion/nit I have is that you could add some kind of asterisk or hover helper to the part when you talk about 'Anthropic's message format', as it did make me want to come here and point out how it's ackchually OpenAI's format and is very common.
Only because I figure if this was my first time learning about all this stuff I think I'd appreciate a deep dive into the format or the v1 api as one of the optional next steps.
Re: Claude Code Unpacked : A visual guide
#143Earlier quoted context omitted.
How many LoC should it be, for that kind of program?
It's a TUI API wrapper with a few commands bolted on. I doubt it needs to be more than 20-50kloc. You can create a full 3D game with a custom 3D engine in 500k lines. What the hell is Claude Code doing?
Comments like these remind me of the football spectators that shout "Even I could have scored that one" when they see a failed attempt.
Sure. You could have. But you're not the one playing football in the Champions League.
There were many roads that could have gotten you to the Champions League. But now you're in no position to judge the people who got there in the end and how they did it.
Or you can, but whatever.
Re: Claude Code Unpacked : A visual guide
#144its April fools joke. this has really gone wide
Re: Claude Code Unpacked : A visual guide
#145Earlier quoted context omitted.
Is there a reason to think it was done by an LLM?
The biggest reason would be: do you know a single developer who could have produced this in a couple of hours?
Yup, strange to see people still don’t understand LLMs massively speed up coding greenfield pet projects. Anytime you see a bee web app it’s better to assume AI use rather than not anymore.
Re: Claude Code Unpacked : A visual guide
#146Earlier quoted context omitted.
How many LoC should it be, for that kind of program?
It's a TUI API wrapper with a few commands bolted on. I doubt it needs to be more than 20-50kloc. You can create a full 3D game with a custom 3D engine in 500k lines. What the hell is Claude Code doing?
Honest question: Why does it matter? They got the product shipped and got millions of paying customers and totally revolutionized their business and our industry.
Engineers using LOC as a measure of quality is the inverse of managers using LOC as a measure of productivity.
Re: Claude Code Unpacked : A visual guide
#147I 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).
Put yourself in their shoes; either the quality of Claude's coding continues to improve or else their business is probably doomed if it stagnates, so for them it makes sense to punt technical debt to the future when more capable versions of their models will be able to better fix it. This is why I personally don't take technical debt arguments about how LLM maintained code bases deteriorate with size/age seriously; i…
I am more worried that we are moving toward creating black boxes and this might turn software "development" into a field as confused as philosophy and dialectics.
Re: Claude Code Unpacked : A visual guide
#148A 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.
Re: Claude Code Unpacked : A visual guide
#149this 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!
Re: Claude Code Unpacked : A visual guide
#150Earlier quoted context omitted.
It's a TUI API wrapper with a few commands bolted on. I doubt it needs to be more than 20-50kloc. You can create a full 3D game with a custom 3D engine in 500k lines. What the hell is Claude Code doing?
Comments like these remind me of the football spectators that shout "Even I could have scored that one" when they see a failed attempt. Sure. You could have. But you're not the one playing football in the Champions League. There were many roads that could have gotten you to the Champions League. But now you're in no position to judge the people who got there in the end and how they did it. Or you can, but whatever.
I don't think this is warranted given that the comment you're criticising is simply expressing an opinion explicitly solicited by the comment it's responding to.