Really interesting parallel between decidedly traditional technology and today.
643 karma · joined April 22, 2016
Really interesting parallel between decidedly traditional technology and today.
In terms of what it changes, it runs some background agents. These can easily be turned on and off via the Dashboard settings as well
Some context on what “rules” are for people who haven’t seen them: Claude Code has a built-in system for structured context beyond claude.md files. Rules support path matching (apply context only to specific files/directories), scoped organization, and structured formatting.
We have been running CodeYam Memory on our own repo for the past few weeks. The main difference we see is fewer repeated mistakes and less manual context maintenance. It’s still early, but it has meaningfully improved how we work with Claude Code.
If discussion gets too long for HN threads, we also have a Discord for questions and feedback: https://discord.gg/eFPUs7CeFw
And here: https://news.ycombinator.com/item?id=47158687#47159087
As a FYI, it looks like this was re-posted more recently which led to some discussion: https://news.ycombinator.com/item?id=47166397
> Second, in retirement interviews, Opus 3 expressed a desire to continue sharing its "musings and reflections" with the world. We suggested a blog. Opus 3 enthusiastically agreed.
For at least the next 3 months, Opus 3 will be writing on Substack
Some discussion on the same post happening here: https://news.ycombinator.com/item?id=47024828
I thought this was an interesting and valid point!
Fascinating! Our team has been blending static code analysis and AI for a while and think it's a clever approach for the security use case the Anthropic team's targeting here.
Fascinating...I wonder what the internal system "Honk" does vs. what Claude Code natively does. Why build an internal system at all? I found the article fairly vague on it beyond this quote; seems like CI/CD and such maybe?
Wild although not entirely surprising. Congrats, Anthropic.
> "Minions are Stripe’s homegrown coding agents. They’re fully unattended and built to one-shot tasks. Over a thousand pull requests merged each week at Stripe are completely minion-produced, and while they’re human-reviewed, they contain no human-written code."
Fully unattended while writing code but with human-reviewed code makes sense, but also seems potentially soulless. I suppose it depends on what they're one-shotting - if it's bug fixes, great. But if it's more creative coding, that might be a bit of a downer for humans who are relegated to reviewing. Curious what others think.
> "When Would You Need This? - Client hands you a Figma Make prototype but not the design file - You want to audit AI-generated code before deployment - You need to migrate away from Figma Make to a different stack - You want to extract design tokens for your design system - Pure curiosity about how Figma structures its data"
Fascinating but not surprising given some of the AI-for-software development changes of late.