Tell me when Chrome will not allow this.

When you ask for something Chrome will not allow, say so immediately instead of trying to build it.

Right now, if a request runs into a platform restriction, the build keeps going. It tries an approach, hits the wall, patches around it, and tries again. Each attempt costs a generation and none of them can ever work, because the limit is Chrome's and not ours.

Examples that come up: Chrome Web Store scripting restrictions, CORS blocking a request to a server that does not allow it, blocking webRequest which Manifest V3 removed, anything needing server-side data acquisition from inside an extension, and reading a page that the browser will not let an extension touch.

What this should do. Recognise the restriction before or during the build and say plainly: this part is not possible in a Chrome extension, and here is why. Then offer the route that does work, for example putting a small server in between, or asking the user for their own key, or using the built-in on-device AI.

Why it matters. The person hitting this cannot tell the difference between our tool being weak and Chrome saying no. So they keep rephrasing the prompt and burning generations on something that was never achievable. It is one of the few ways a build can fail where telling the truth early is far more valuable than trying harder.

Raised in a five taco review from a non developer who built a full extension with Supabase, a side panel and AI analysis. 4 September 2026.