A short read on the topic's time range, peak episode, and strongest associations. Use it as the quick orientation before drilling into examples.
Claude Code appears in 78 chunks across 34 episodes, from 2025-03-17 to 2026-04-20.
Its densest episode is Bits and Bobs 2/2/26 (2026-02-02), with 6 observations on this topic.
Semantically it travels with Claude, llms, and prompt injection attack, while by chunk count it sits between ground truth and mental model; its yearly rank moved from #10 in 2025 to #4 in 2026.
Over time
?
Raw mentions over time. Use this to see absolute attention, not relative rank among all topics.
Range2025-03-17 to 2026-04-20Mean2.3 per episodePeak6 on 2026-02-02
Observations
?
The primary evidence view for this topic. Sort it chronologically when you want concrete examples behind the larger pattern.
Showing 78 observations sorted from latest to earliest.
...his time using LLMs incidentally in attack chains:
Nx compromised: malware uses Claude code CLI to explore the filesystem
zack_overflow: "A popular NPM package got compromised, attackers updated it to run a post-install script that steals se...
Last week I mentioned that Claude Code inserts <system-reminder> a lot.
Apparently it also removes old ones from the chat history, so they're only towards the end, on the current task.
Tha...
Claude Code is an interesting chat-adjacent UX modality.
It presents as a chat but it does a ton of things under the covers.
It's not just chat, it's a chat summ...
Someone peeked inside of Claude Code's workings and saw tons of "<system-reminder>" instructions, keeping it convergent and on track.
That technique could also be used by prompt injectio...
A few months ago Simon Willison called Claude Code a honey badger.
I missed this then but it resonates for me.
It barrels forward, smashing through things it doesn't understand yet.
Powerful but kind ...
A mashup I want: Claude Code + Obsidian + UI + multi-player[en].
Strap on a self-improving ecosystem and you get something that could change the world.
The faster you have Claude Code write code, the farther away you get from understanding the code.
The harder it is for you to analyze it, fix bugs in it, extend it.
There's more to ...
...fetch things from the gopher protocol.
Gopher felt like a precursor to the web.
Claude Code's ability to blossom software feels like gopher.
What's the web in this parallel?
Claude Code feels like a ride-on mower.
At first you go "Whoa, this is so easy to use, I can do 10x more than I could before."
But as you use it for more things ...
Making agents as a way to bound data is a useful pattern.
Claude Code does this a lot, spinning up little sub-agents that are isolated from the main flow often.
The agent is a secure little compute environment that boun...
... issues.
The comments are mostly negative.
In this Hacker News thread about how Claude Code will route around restrictions the user set on `rm`, most of the response is, "yeah but of course it can, the user should not be surprised."
People r...
... coding agents: the cascading self-destruction debug loop.
I had a session with Claude Code on a personal project that did a pretty good job (with a few nudges) of adding a significant new feature.
But it left a single, minor, linting error....
Coding with Cursor or Claude Code is tiring in a different way than normal programming.
Normal programming has architectural thinking and also tactical programming.
The tactical progr...
Claude Code is powerful but hard to control.
You can't really see where it's going to steer it.
So much of what it's "thinking" is not shown to you as a user.
Li...
Claude Code is kind of like a ride-on mower with a stuck accelerator and a loose steering wheel.
Very powerful, and if you need a general result in an open lawn ...