Live data from Hacker News

Claude Code Unpacked : A visual guide

ccunpacked.dev

411–420 of 464 posts

Re: Claude Code Unpacked : A visual guide

#411
post #321

Earlier quoted context omitted.

>> It would be insane to code anything by hand these days. I strongly disagree, but it made me chuckle a bit, thinking about labeling software as "handmade" or marketing software house as "artisanal".

Our organic artisanal code is written by free-range developers

"free-range" means fully remote, right?

Re: Claude Code Unpacked : A visual guide

#412
post #318

Earlier quoted context omitted.

"Even I would have scored that goal" == "I would never ever have created a bloated mess like Anthropic" You just repeat the same statement. That bloated mess is what got them to the Champions League. They did what was necessary to get them here. And they succeeded so far. But hey, according to some it can be replicated in 50k lines of wrapper code around a terminal command, so for Anthropic it's just one afternoon of…

> Even I would have scored that goal" == "I would never ever have created a bloated mess like Anthropic" Since you keep putting words in my mouth that I never said, and keep being deliberately obtuse, this particular branch is over. Go enjoy Win11 written by same level of champions or something. Adieu.

Ah, Winning Eleven.

Not what you were referring to.

Re: Claude Code Unpacked : A visual guide

#413

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…

This is actually a GREAT example of vibe-coding + skill.

Re: Claude Code Unpacked : A visual guide

#414

Earlier quoted context omitted.

Herding cats is treating the LLM's context window as your state machine. You're constantly prompt-engineering it to remember the rules, hoping it doesn't hallucinate or silently drop constraints over a long session. System-level governance means the LLM is completely stripped of orchestration rights. It becomes a stateless, untrusted function. The state lives in a rigid, external database (like SQLite). The database…

> The database dictates the workflow, hands the LLM a highly constrained task, and runs external validation on the output before the state is ever allowed to advance. This sounds like where lat.md[0] is headed. Only thing is it doesn't do task constraint. Generally I find the path these tools are taking interesting. [0] https://github.com/1st1/lat.md

I looked into lat.md. They are definitely thinking in the same direction by using a CLI layer to govern the agent.

The key difference is the state mechanism. They use markdown; I use an AES-encrypted SQLite database.

Markdown is still just text an LLM can hallucinate over or ignore. A database behind a compiled binary acts as a physical constraint; the agent literally cannot advance a task without satisfying the cryptographic gates.

I just dropped the Show HN for it here if you want to check out the architecture: https://news.ycombinator.com/item?id=47601608

Re: Claude Code Unpacked : A visual guide

#415
post #408

Earlier quoted context omitted.

Some of your comments have already been marked as "dead" oddly enough that just seemed like normal comments explaining your rationale. edit: Also seems like peoples replies are getting downvoted to hell and getting marked as dead and dissapear. Someone must not like your idea :-)

Comments are marked dead by automatic processes, not through downvotes. They're dead before anyone sees them, and you can't vote on a dead comment. amangsingh's comments have probably triggered some automated moderation. Probably at least partially because they sound LLM-generated.

Spot on regarding the automod. Unfortunately, the way I naturally structure my writing almost always triggers a 50/50 flag on AI content detectors. It is the absolute bane of my existence.

The filter instantly shadowbanned the Show HN post when I submitted it, which is why the link was dead for a while. Thankfully, human mods reviewed it and restored it. The link is fully live for a while now!

Re: Claude Code Unpacked : A visual guide

#417

Earlier quoted context omitted.

Of course I expect it is vibe coding. It would be insane to code anything by hand these days. But that doesn't mean there is no creative input by the author here.

You well on the path to AI-fueled psychosis if you genuinely believe this.

At least it's more productive than AI Derangement Syndrome.

Re: Claude Code Unpacked : A visual guide

#418
post #293

Earlier quoted context omitted.

Guess what? People have ZERO reason to Open Source anything now.

This said Jeavon's Paradox will likely mean far more code is open sourced simply due to how much code will get written in total.

We should be applauding the promotion of science and useful arts that genAI is fueling.

But egos are involved.

Re: Claude Code Unpacked : A visual guide

#419

Earlier quoted context omitted.

https://x.com/trq212/status/2014051501786931427 " Most people's mental model of Claude Code is that "it's just a TUI" but it should really be closer to "a small game engine". For each frame our pipeline constructs a scene graph with React then -> layouts elements -> rasterizes them to a 2d screen -> diffs that against the previous screen -> finally uses the diff to generate ANSI sequences to draw We have a ~16ms fram…

Do they reconstruct the scene graph for each frame?! Maybe I'm overinterpreting the phrasing. Someone take a peek at the source?

Not reliably.

Re: Claude Code Unpacked : A visual guide

#420
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
Post reply on HN