A strict URL-to-origin helper exists next to the claude.ai origin code, with nothing calling it.
An origin normaliser that upgrades websocket schemes and allows plain http only for loopback has no callers.
What's wrong with this entry?
A new function beside the claude.ai origin resolver turns a URL into a bare scheme-and-host origin. It upgrades wss: to https:, allows ws: and http: only for loopback hosts (localhost, 127.0.0.1, ::1 or any 127.x.x.x address), and returns nothing if the URL carries credentials, a path, a query or a fragment.
- Its symbol appears only at its own definition in the bundle; nothing calls it.
- The neighbouring origin-override hook that the resolver consults has a body of a bare
return;, so it always yields nothing and the resolver always falls back to the configuredCLAUDE_AI_ORIGIN. - Together these look like groundwork for a configurable or localhost artifact origin that nothing selects yet.
"wss:"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.