I recently vibe-coded a very small open-source Chrome extension called Direct GO (GitHub: https://github.com/LuoShenKui/DirectGO). The idea is intentionally simple: a custom New Tab page focused on fast access and navigation. It is inspired by command palettes and AI-assisted suggestions, aiming to take users directly to relevant pages instead of always starting from the search engine homepage. In practice, it does not fully bypass Google or Bing. In many cases it still opens their result pages directly, and in others it only skips the initial homepage (and its ads). Any more complex routing depends on large language models. During Chrome Web Store review, the extension was rejected under the Single Purpose policy (Red Argon). The feedback was: * Please modify your extension to provide a single, clear purpose. * If your New Tab page contains a search experience, it must use the Chrome Search API to respect the user’s selected search provider. * If you want to modify both the New Tab page and the default search provider, they must be split into separate extensions. What surprised me is that: * the extension does not explicitly change the default search engine, * it does not inject ads or monetize search, * and it does not attempt to replicate Google Search. I do acknowledge that the project explores ways to reduce reliance on the traditional search results list. However, it does not actually replace search engines. In most cases, it still opens Google or Bing result pages directly. Yet it seems that any search-like interaction on the New Tab page is treated as crossing a hard boundary. My takeaway so far is that the real policy line is not “changing search settings”, but “introducing any alternative search-adjacent path on the New Tab page that could divert usage from Google Search”. At this point, I’m trying to decide what to do next. The options seem to be: * remove anything resembling search and reduce it to a pure navigation / command-style tool, * split functionality into multiple extensions, * or abandon this idea on Chrome entirely. For people who have built Chrome extensions or dealt with similar reviews: Is there a realistic path to iterate on a search-adjacent New Tab tool within Chrome’s rules, or is this simply a dead end by design?