[BUG] the Claude extension update (v1.0.66) broke fedex.com access that was working on v1.0.65 yesterday
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I am using Claude Code desktop and connecting to Chrome via the beta extension. Yesterday, I was able to access tracking on FedEx public urls and write data back to a sheet on my computer. Today, after the desktop updated, the extension appears to be blocking the website access. Permissions are set to allow Claude access to all sites, there are no blocked or approved sites listed.
key details are:
Extension version: 1.0.66 (updated today April 7, 2026)
Issue: navigate tool returns "Navigation to this domain is not allowed" for fedex.com
Worked on: v1.0.65 (yesterday April 6)
Use case: Automated FedEx tracking lookup for business fulfillment operations
Site access setting: "On all sites" — no blocked URL patterns configured
Impact: Breaks a scheduled automation that was running successfully
What Should Happen?
Claude should lookup tracking via tracking links sent through Gmail, parse ship-to city and state, write it back to a file on the desktop, then fill in a sheet in google drive.
Error Messages/Logs
Error Message:
Navigation to this domain is not allowed
Steps to Reproduce
Steps to Reproduce:
Open Claude Code desktop app or CLI
Ensure Claude in Chrome extension is connected (MCP tools available)
Call tabs_context_mcp to get/create an MCP tab group
Call navigate with any fedex.com URL, e.g.:
navigate(url: "https://www.fedex.com/fedextrack/?trknbr=380288819591", tabId: <any_tab_id>)
navigate(url: "https://www.fedex.com/fedextrack/?trknbr=380288819591&trkqual=12030~380288819591~FDEG", tabId: <any_tab_id>)
Both return: Navigation to this domain is not allowed
Extension Settings Verified:
Site access: "On all sites"
No blocked URL patterns configured
Approved sites list: empty (was reset by the update)
Extension Permissions page shows no domain restrictions
What Worked Previously:
On v1.0.65 (April 6, 2026), the same navigate calls to fedex.com worked successfully
The agent navigated to FedEx tracking pages, read destination city/state data, and used it to match shipment records
Example URL that worked yesterday: https://www.fedex.com/fedextrack/?trknbr=380118443438&trkqual=12030~380118443438~FDEG
Execution Log (from April 6 — working):
Multiple successful doPost Web App executions at 7:21 PM, 7:30 PM, 7:37 PM, 7:38 PM on April 6 that processed FedEx-enriched tracking data with destination city/state values
Execution Log (from April 7 — broken):
Agent attempted navigate to fedex.com URLs and received "Navigation to this domain is not allowed" for every attempt
All tracking entries were posted to the webhook with empty dest_city/dest_state fields because FedEx data could not be retrieved
Impact:
This breaks a scheduled business automation that:
Reads fulfillment emails from a dropship supplier (New Country Organics)
Looks up FedEx tracking destinations to match shipments to customer orders
Posts enriched data to a Google Apps Script webhook that updates a tracking spreadsheet
Without fedex.com access, the destination city/state cannot be determined, and the system cannot reliably match tracking numbers to the correct orders when multiple orders share the same SKU.
Note: This is a dropship fulfillment use case — we are not the shipper, so we cannot use the FedEx API (requires shipper credentials). Web-based tracking lookup is the only available method.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
v1.0.65
Claude Code Version
v1.0.66
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
Environment:
Claude in Chrome extension v1.0.66
Google Chrome, Windows 11 Home 10.0.26200
Claude Code desktop app (claude-opus-4-6 model)
Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗