Why does Magento need Claude Code over Copilot?

Magento is a deep PHP codebase where the answer to almost any question lives across 5 – 15 files: a controller in `app/code/`, an interface in `vendor/magento/framework/`, a generated factory in `var/di/`, an event subscription in `etc/events.xml`, a plugin in another module’s `etc/di.xml`. Claude Code reads all of those by default; Copilot reads the active editor and a small surrounding window.

Concrete examples where Copilot routinely fails on Magento:

• “Add a custom attribute to product save flow” — needs to find existing observers, plugins around `Product::save()`, and the right entity_type. Claude Code finds them in vendor and proposes the correct extension point. Copilot suggests editing `Product.php` directly (vendor edit — disaster).
• “Why is this category page slow?” — needs to trace through layered nav, indexers, full-page cache. Claude Code reads all the relevant files. Copilot guesses.
• “Generate the db_schema.xml for this new module” — needs to know the format precisely and link to the module’s composer.json. Claude Code gets it right; Copilot often produces invalid XML.

It’s not that Copilot is bad — it’s that Magento’s shape rewards filesystem access and ground-truth reading, which is Claude Code’s home turf.