Laravel Boost pushes Cloud pitch, angers devs

This is a small edit with outsized optics: when your product ships agent instructions, every default becomes a distribution channel. The backlash is predictable because Boost is supposed to improve code quality, not steer teams toward a single vendor.

• –The PR adds a deployment section to Laravel’s core AI guideline, explicitly elevating Laravel Cloud in the suggested workflow.
• –Commenters say it “poisons” their agents, since they now need to override core guidance to avoid vendor bias in generated recommendations.
• –Laravel Boost’s real value is its Laravel-specific MCP tools and curated docs, so trust in the default instructions matters more than ordinary README copy.
• –Laravel Cloud may be a legitimate deployment option, but putting the pitch into agent-facing guidance blurs the line between documentation and ads.
• –This is a preview of a bigger problem: agent prompts and guidelines are becoming a new marketing surface, and teams will increasingly fork or audit them like code.