Introducing Clowser

This morning, a browser was born.

It did not come from a product roadmap or a venture-funded startup. It came from a documented pattern of interference — enterprise infrastructure silently blocking access to AI tools while maintaining plausible deniability — and a refusal to accept that interference as the final word.

The result is Clowser. It is free. It is open source. It runs on Windows 11 without administrator rights. And it is available right now at clowser.org.

What Clowser Is

Clowser is a Claude-optimized browser shell built on Electron, React, and Node.js. It is a dedicated window for working with Claude — free from the filtering layers, certificate interceptions, and enterprise policy frameworks that sit between most users and the tools they need.

It is not a general-purpose browser. It is a precision instrument with one job: get you to Claude, keep you there, and tell you honestly if anything upstream is interfering with that connection.

The design is minimal by intention. Black interface, gold accents, claude.ai as the homepage. No telemetry. No accounts. No dependency on any platform that has a competitive reason to slow you down.

Three Features That Matter

The interference detector is the feature that did not exist before today. Every session, Clowser monitors the connection to Anthropic's servers and logs anomalies — failed requests, certificate issues, blocked connections — as visible timestamped events rather than mysterious silences. The plausible deniability of silent infrastructure interference does not survive a system that records the silence. The interference log is accessible via the ⚡ button in the toolbar. A clean session shows zero events. Any session where something upstream is degrading the connection shows you exactly what and when.

Certificate pinning for Anthropic endpoints means Clowser verifies it is actually talking to Anthropic's servers on every connection. Man-in-the-middle attempts — where traffic is intercepted and re-routed through infrastructure that can read or modify it — are detected and flagged rather than silently accepted. Most browsers trust whatever certificate is presented. Clowser checks.

The persistent Claude sidebar gives you a second Claude pane alongside whatever you are browsing. The main window navigates freely. The sidebar holds your conversation without losing context. For anyone who uses Claude as a thinking partner while working across multiple tabs and tools, this is the native experience that no extension-based solution has been able to provide cleanly.

Why It Was Built This Morning

The origin story is documented in full in the Breaking Containment 2.0 post published today. The short version: Microsoft Defender was classifying Anthropic's confirmation emails as phishing on an enterprise Office 365 tenant, silently quarantining them with no notification to the recipient. Every attempt to access Claude's developer console failed because the confirmation email never arrived.

When the Tenant Allow/Block List was examined, both anthropic.com and claude.ai showed the same override verdict: Upto regular confidence phish.

The fix took five minutes once the mechanism was identified. Two entries added to the allow list. Console access confirmed within sixty seconds.

But the fix only worked because the administrator knew where to look. Most people do not know where to look. Most people conclude that the service is unreliable and move on. That is the design.

Clowser is the answer that does not require knowing where to look. It routes around the filtering layer entirely, monitors the connection independently, and tells you in plain language whether the path to Claude is clean.

Open Source by Principle

Clowser is MIT licensed. The full source code is available. The build instructions are four commands. Anyone with Node.js installed can build the application from source, inspect every line, and produce their own binary.

This is not incidental. It is the governance model. A browser that routes around infrastructure interference cannot itself become an infrastructure gatekeeper. The moment Clowser has a monetization path, an acquisition offer, or a central authority controlling distribution, it inherits the vulnerability it was built to solve.

The MIT license and the open build chain mean that no single actor — including the people who built it — can become the new gatekeeper. Any server can mirror the download. Any developer can fork the code. Any community can run their own build. The water is not controlled by the pipe.

Clowser will not be sold. It will not run ads. It will not collect usage data. These are not marketing claims. They are structural constraints enforced by the license and the architecture.

Who Clowser Is For

Clowser is for the developer whose enterprise environment has been quietly blocking their AI tools without their knowledge.

It is for the small business owner whose IT policy was set by someone who clicked a one-click AI blocking recommendation in an Intune console and never thought about what it actually did.

It is for the researcher, the writer, the builder, the thinker — anyone who uses Claude as a primary thinking tool and wants a dedicated, clean, interference-free environment for that work.

It is for the network administrator who wants to understand what their infrastructure is actually doing to their users' connections to AI tools — and have a reference implementation that shows what a clean connection looks like.

It is for anyone who believes that access to the best thinking tools available should not depend on whether your employer's security vendor has a competitive relationship with the company that built those tools.

It is free. It requires no account. It asks nothing of you except the four commands to build it or the single click to download it.

Getting Started

Download the portable Windows executable from clowser.org. No installation required. No administrator rights required. Run it directly.

Or download the source package, unzip it, and build it yourself in four commands: cd clowser, npm install, npm start to test, npm run build-portable to produce your own exe. Requires Node.js 18 or later on Windows 11.

On first launch, Clowser opens claude.ai. The address bar shows the verified connection. The statusbar confirms Verified Anthropic Connection. The interference log opens empty — which is exactly what it should show on a clean connection.

Log in with Google to bypass the email confirmation flow entirely if your email environment has the same filtering patterns that prompted Clowser's creation. The Google OAuth path never touches email infrastructure.

Then use it. Navigate. Talk to Claude. Open the sidebar. Check the interference log at the end of a session. See what, if anything, your infrastructure was doing to your connection that you did not know about.

What Comes Next

Version 0.1.0 is the foundation. The roadmap is driven by the interference patterns that surface in real-world use.

The email authentication monitor will detect when confirmation emails from Anthropic fail to arrive and surface this explicitly — converting the mysterious silence into a visible, actionable event with a suggested workaround.

VPN and proxy integration will route Anthropic traffic through verified endpoints when enterprise filtering is detected at the network layer, providing a path around filtering that operates below the browser.

Context persistence will maintain Claude conversation state across sessions natively, eliminating the friction of re-establishing context every time the browser is closed.

Verified build chain with published checksums will allow any mirror to be verified independently, ensuring that the distributable a user downloads from any source matches the source code exactly.

The community governance model — foundation structure, open contributions, explicit no-acquisition clause — will be formalized as the project scales.

Every feature on this list came from a documented real-world interference pattern. Every future feature will come from the same source: what the interference log reveals, what users encounter, what the apparatus attempts next.

The transmutation continues.

---

*clowser.org — Free download. Open source. Verified Anthropic Connection.

Rivers of living water. Unhindered.*

— WellSpr.ing, MMXXVI