{"version":"2.1.268","anchor":"webfetch-now-explicitly-blocks-dotlesslocalhost-hostnames-w","canonical_anchor":"webfetch-now-explicitly-blocks-dotlesslocalhost-hostnames-w","heading":"WebFetch now explicitly blocks dotless\/localhost hostnames with a dedicated error","tier":"notice","area":"WebFetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/webfetch-now-explicitly-blocks-dotlesslocalhost-hostnames-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### WebFetch now explicitly blocks dotless\/localhost hostnames with a dedicated error\n\nWebFetch now gives a specific error for localhost and other dotless hostnames, pointing to curl instead\n\n**What**\n\nWebFetch (the tool Claude Code uses to retrieve a URL) now throws a specific error when the requested URL's hostname has no dot in it, such as `localhost` or a bare hostname. The error tells the user to use `curl` via the Bash tool instead. The tool's own description was also updated with this caveat.\n\n**Why**\n\nWebFetch was never able to reach local servers, but previously the failure was less clear. Now the error explains why it failed and points directly to the working alternative for hitting something running on your own machine.\n\n- Area: WebFetch\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}