A new software paradigm for the AI age
New ideas to help you build the future—in your inbox, every day.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Read the original article
Comments
Why should I bother to read an article that the "author" didn't write? Might as well just go prompt Claude. Or is this about saving tokens?
By brap 2026-02-0212:48 I don’t see it as the author being lazy, actually the opposite, I see it as being performative and a tryhard. Either way it’s annoying and doesn’t make me want to read it.
After looking into it, as I suspected, the author seems to make his living by selling people the feeling that they’re in the cutting edge of the AI world. Whether or not the feeling is true I don’t know, but with this in mind this performance makes sense.
I like the "coauthored by Claude" notice just above the "read with Claude" button.
So I can have an article summarized by AI that was written by AI and is also about AI.
By ThatMedicIsASpy 2026-02-0212:58 I check the url of those buttons and the prompt alone justifies a route to 127.0.0.1
By Lerc 2026-02-0212:51 My thought was that to do applications with agents, what you really need is a filesystem and perhaps an entire access rights policy that can handle the notion of agent-acting-on-behalf-of
I'm not sure if Unix groups could be leveraged for this, it would have to be some creative bending of the mechanism which would probably rile the elders.
Perhaps subusers or co-users are needed. They have their own privilege settings and can do the intersection of their own privileges and the client for which they act.
The main distinction would be the things they create are owned by their client, and they can potentially create things and then revoke their own access to them effectively protecting things from future agent activity, but leaving all of the control in the users hands.
