Detailed Analysis
A developer using Claude Code has released version 4 of the wearehere browser extension, shifting the tool from passive privacy scanning to active cookie management. The core new feature is an automated "cookie scoper" that enforces expiration limits on browser cookies: long-lived cookies are capped from 365 days down to 7 days for untrusted sites, known analytics and advertising cookies are demoted to session-only status, and third-party cookies are cleared when a tab is closed. Trusted domains can be exempted with a single click, granting 30 or 90-day windows. The extension operates entirely locally, with no accounts, telemetry, or remote rule lists, and is released under the Apache-2.0 license with source code available on GitHub.
The transition from v3 to v4 represents a deliberate philosophical shift in the extension's design. Where v3 delivered information — surfacing which trackers were present and generating privacy reports — v4 intervenes in the tracking lifecycle itself. The developer has also significantly simplified the interface, reducing the popup from eight cards to three focused blocks and collapsing the dashboard from six tabs to three. Crucially, vocabulary describing tracker types has been standardized into five concrete categories: cookies, pixels, device fingerprinting, typing patterns, and click behavior. This reduction in abstraction addresses a common usability problem in privacy tools, where vague terminology like "trackers" leaves users uncertain about what is actually being measured or blocked.
The extension is explicitly positioned as a complement to, rather than a replacement for, request-blocking tools like uBlock Origin. This layered approach reflects a maturing understanding of the browser privacy ecosystem, where different threat vectors require different technical interventions. Request blockers prevent tracking scripts from loading at all; cookie scopers limit the persistence of tracking data that does accumulate. By focusing exclusively on the cookie layer, wearehere avoids the arms-race dynamics of blocklist maintenance while targeting the mechanism that enables long-term cross-session user recognition.
The project's construction using Claude Code situates it within a growing pattern of individual developers leveraging AI coding assistants to produce sophisticated, security-relevant software outside traditional institutional contexts. Privacy tooling of this complexity — involving browser storage APIs, cross-session state persistence, and nuanced domain-trust logic — has historically required significant specialized knowledge. The fact that a single developer could build and maintain such a tool while also handling UX consolidation across multiple releases suggests that AI-assisted development is meaningfully lowering the barrier to entry for security and privacy software, expanding the range of contributors capable of shipping functional, auditable open-source tools in this domain.
Read original article →