User installs the extension, navigates to the Cookie Clicker game page (orteil.dashnet.org/cookieclicker/), clicks the extension popup, and toggles automation checkboxes (auto-click, auto-buy, notifications, game speed). Settings persist via chrome.storage.sync and are sent to the content script running on the game page.

Target users: Cookie Clicker players who want to automate repetitive game actions

The extension's own gameClient.js file was only partially read (180 of 459 lines), but the config, popup, and manifest provide sufficient evidence for all three decisions.
No network requests to external services were found beyond the Cookie Clicker game URLs themselves, confirming no authentication or payment infrastructure exists.

Monetization

No paid features detected

The extension is fully free with all features available to all users. There are no payment gates, no premium/pro tiers, no subscription prompts, no Stripe/billing integration, and no license checks. All keyword hits for 'upgrade', 'pro', 'stripe', 'license' are false positives: 'upgrade' refers to Cookie Clicker in-game upgrades (auto-buy game upgrades), 'pro' and 'stripe' come from Bootstrap CSS library (progress-bar-stripes, progid filters), and 'license' refers to Apache/MIT open-source licenses of bundled libraries.

Confidence: 95
Payment platform: --
Source: AI / High
Login required: No
Reason: The extension operates entirely locally within the browser. It injects content scripts into Cookie Clicker game pages and provides a popup UI with checkboxes to toggle automation features. Settings are stored via chrome.storage.sync. No login UI, authentication flow, token handling, or account creation exists in any source file. The destination site (Cookie Clicker at orteil.dashnet.org) does not require an account to play.

Permission risk

Medium-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

扩展能力较强：tabs、storage
同时具备浏览数据与站点访问能力

Publisher

Naoto Yokoyama

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access