> The app does absolutely no work in the background. It works by simply existing as a running process, thanks to having the same bundle identifier as the Music app.

I love clever, low-or-no-code engineering solutions like this. You typically need to understand a systems very deeply to reach this level of elegance. In this case, one has to understand exactly what happens when the play button is pressed in Mac OS, how bundle identifiers work, etc. And the outcome is an app with almost no code at all – just a collision – it's beautiful.

(As an aside, coding agents are terrible at this kind of thing; I'd guess Codex as of right now would write some overpowered application that polls in a loop looking for Music App starts and killing them)

On the contrary, this feels like a great (hypothetical) example of how to use coding agents effectively.

> Codex as of right now would write some overpowered application that polls in a loop looking for Music App starts and killing them

Most human engineers would also do this. It's a relative rarity to find someone writing things this elegantly.

Similarly, if you asked an agent to "Stop the Apple Music app from launching", it would likely try to do what most humans would do. Otoh if you asked an agent to explain why the Apple Music app launches, based on the discoveries it presents to you from its investigation you would quickly discover for yourself that asking it to make a zero code app that collides with Music is the best course of action.

Reminds me that when I was in high school, my father used to regulate my gaming sessions with Apple ScreenTime. I changed the BundleIdentifier in my game's info.plist to `com.apple.systempreferences` and sign the .app with my own developer cert to bypass this. Was a lot of fun before got caught physically.

Myyy codex with my skills would never! Never do such a thing.