Apple is not what it used to be… We see it in the hardware AND the software.
It used to be: think different
It used to be: It just works…
Now we got “apple intelligence” and subscriptions all over the place and also the lock-in feels stronger over time. Don’t even get me started that one can’t easily replace the battery oneself. They gradually convinced us that reduced repairability is fine.
I got my first MacBook Pro in 2006… things were quite different back then.
Anyway, I’ve decided I wanted to get away from BigTech a while ago. Apple is the hardest part for me. They used to have this annoyance-free usability that I loved so much. iPhone Duo, Touchscreen on the Mac, liquid glass, visionPro, etc. are all valid things to go after and I don’t think these are bad things per se. But it is not what I care about. And clearly the focus has shifted away from the values I used to share with this company about what constitutes a good product.
I took the hit on the ownership/control side because their products were so ‘seamless’.
Now I hope the Framework and Fairphone (with eOS) have matured enough to not regret when I am getting off the Apple-train. I don’t expect a frictionless experience - it just has to be sufficiently annoyance-free. I’ll happily take some rough edges in exchange for greater control and ownership.
“Unfortunately” their products are really sturdy and it will take a while until my M3 MacBookAir and iPhone 14 need to be replaced ^^
This project uses `AGENTS.md` as its agent instruction file (kept provider-agnostic).
Treat any `AGENTS.md` file exactly as you would a `CLAUDE.md` file — at the root level and in any subdirectory you are working in.
I don't think this will work reliably. Pretty sure it's not the LLM deciding to read the files, it's the harness in Claude Code itself injecting the instructions files based on the paths the model accesses.
Edit: sometimes if Claude lists files in a directory or does a search that shows it an AGENTS.md exists it will decide to read it. But it's not a reliable behavior.
On many filesystems, a lot of data about a file is not attached to the content of the file, but stored in a master filename and metadata table graph tree of some sort, and the address offset within that metadata used to retrieve the contents on disk can be a duplicate of another entry, without that situation instantly leading to a filesystem driver crash. Some filesystems officially support such duplicates as well as equivalents of HTTP 3xx, some you can just do as a matter of fact and fsck would have some words about it.
Default filesystems for all Unix, Linux, WinNT, all do.
Yes. The thing is that creating a link will not do it recursively for all subdirectories. Even worse, in the subdirectories I didn't want to place a claude.md in the first place but just have agents.md.
That was the idea.... For the toplevel it works because of the @AGENTS.md and this is also the part the link would solve.
I phrased it wrong. It was not about "automatically detect nested AGENTS.md". The idea was that when AGENTS.md files should be treated just like CLAUDE.md files in all subdirectories, when encountered.
Anyway, with the change they announced, I can now simply delete my CLAUDE.md and everything will just work the way I wanted.
What I meant is that the LLM isn’t the one that loads the agent file. It’s not trained to look for CLAUDE.md. It’s only training is to edit that file, and the harness does the magic of injecting it. So I would predict that with those instructions it rarely or only intermittently loaded AGENTS.md, but if you asked it to add a rule it would probably have put it on the right file.
Post author just wanted quick clicks based on kneejerk heuristics based attacks on Bend. Now he’s doing gymnastics all over this thread to mitigate what he said. Sad and disappointing.
Yes, I used Bend as an example because it is recent and high profile, and I also wanted to present my issues with it. I did not mean to conflate it with the main idea I was trying to present to the degree that I obviously did after reading my own writing as a third party would (at least to the degree that it is possible to do so).
Your only issue was that the author was unaware of a subject and that the code is long. You didn’t even google the guy! Respectfully, I think you made a bad point and probably harmed your own stance with this post.
uff.. HN is degrading rapidly. (Yes, also all your comments about "AI SLOP SPOTTED, AI;DR". Regurgitating the same crap over and over again.... pff...)
It used to be: think different
It used to be: It just works…
Now we got “apple intelligence” and subscriptions all over the place and also the lock-in feels stronger over time. Don’t even get me started that one can’t easily replace the battery oneself. They gradually convinced us that reduced repairability is fine.
I got my first MacBook Pro in 2006… things were quite different back then.
Anyway, I’ve decided I wanted to get away from BigTech a while ago. Apple is the hardest part for me. They used to have this annoyance-free usability that I loved so much. iPhone Duo, Touchscreen on the Mac, liquid glass, visionPro, etc. are all valid things to go after and I don’t think these are bad things per se. But it is not what I care about. And clearly the focus has shifted away from the values I used to share with this company about what constitutes a good product.
I took the hit on the ownership/control side because their products were so ‘seamless’.
Now I hope the Framework and Fairphone (with eOS) have matured enough to not regret when I am getting off the Apple-train. I don’t expect a frictionless experience - it just has to be sufficiently annoyance-free. I’ll happily take some rough edges in exchange for greater control and ownership.
“Unfortunately” their products are really sturdy and it will take a while until my M3 MacBookAir and iPhone 14 need to be replaced ^^