[BUG] To: Anthropic Support Subject: Claude (Claude Code desktop app) failed to deploy my website and connect my domain; hours wasted

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?

To: Anthropic Support
Subject: Claude (Claude Code desktop app) failed to deploy my website and connect my domain; hours wasted

Date of session: 5 October 2026
Product: Claude desktop app, Code tab (Claude Code), model Opus 5.5
Task: Build a Hebrew B2B wholesale website, upload it to my Bluehost hosting, and connect my domain bigdayavoda.com (registered at Namecheap).

Summary
Claude built the site content: a static HTML catalog and later a WordPress/WooCommerce store with 3,822 products. But it could not complete the deployment or the domain connection. The process took many hours, needed constant manual help from me, and ended with me hiring a human developer. Some failures were in the tools Claude uses; others were Claude's own mistakes or missing knowledge.

Part A – Tool / platform failures

Built-in browser stops working when the window is not in front. When the Claude window was minimized or behind another window, pages stopped rendering. Screenshots and clicks timed out. I had to keep the Claude window in the foreground for every step, and Claude repeatedly asked me to do so.
The Claude in Chrome extension could not read any page. It was connected to my Chrome, but every screenshot, page-text read or page action on Bluehost, cPanel and Namecheap failed with "script injection timed out". The same pages worked normally for me.
Bluehost single sign-on never loaded in the built-in browser. cPanel, "Edit Site" and the WordPress installer go through a Bluehost login page (nfhostingapp.com). It stayed on "Loading..." indefinitely in Claude's browser.
New tabs and popups opened by websites were blocked. Bluehost's cPanel button, the WordPress installer and the domain-connection authorization (Entri → Namecheap login popup) all open new tabs or windows. Claude's browser blocked them, so I had to click them myself.
Claude could not upload files from my computer. The built-in browser cannot use a file picker. I had to upload index.html to cPanel and choose the CSV file for the WooCommerce import myself.
Typing into a third-party chat did not work. Claude opened Bluehost's live-agent chat, but the text it typed into the chat box (a cross-origin iframe) never registered, so it could not talk to support for me.
Viewport and scaling kept changing. The browser pane changed size and zoom between screenshots, so click coordinates were wrong several times.
Part B – Claude's own mistakes and missing knowledge

Wrong order of steps for the domain. It told me to create the domain in cPanel before changing the nameservers at Namecheap. cPanel rejected it ("domain points to an IP that does not use the DNS servers associated with this server").
Wrong assumption about Bluehost's tools. It told me to install WordPress through "Softaculous" in cPanel. Bluehost's cPanel does not have Softaculous, so I searched for nothing.
Duplicate WordPress installs. Repeated clicks on Bluehost's "Add Website" during slow loading created three WordPress sites instead of one. Two empty "Welcome" sites are still in my account.
Deleting the old site removed the domain. Claude had me delete the old "Other CMS" site that held bigdayavoda.com. This also removed the domain from Bluehost's domain list. After that, the "Connect Domain" wizard showed "Not available to be connected", and Claude did not know how to fix it.
Manual DNS edits did not take effect. Claude edited the A records in Bluehost's DNS panel to point to my server IP. Bluehost's nameservers still served the old parking IP more than an hour later. Claude could not explain why.
Data import bug. Category names containing commas were split into separate categories by the WooCommerce importer, giving 88 categories instead of 47. Claude fixed it afterwards, but it should have escaped the commas in the CSV beforehand.
Guessing instead of knowing. It tried a password reset with an email that turned out not to be the WordPress admin email. It also guessed several Bluehost page URLs that returned errors (502 / 404).
Too many retries and too much waiting. It retried failing browser actions many times before telling me plainly that it could not do the task.
It ran a multi-agent research workflow without asking me first. It disclosed this afterwards.
Part C – Result

The site content is complete. WordPress/WooCommerce is installed with 3,822 products, the homepage, WhatsApp and quote buttons, and quote emails to my address.
The domain bigdayavoda.com is still not connected to the site. The site is not live, and the "Coming Soon" page is still active.
I had to hire a human developer to finish the job.
Requests

Make the built-in browser keep working when the app is in the background.
Fix the Chrome extension so it can read and control pages the user is signed in to.
Allow popups and new tabs for sign-in flows the user starts (SSO, OAuth, domain-connection services).
Allow file uploads from the session's own folders in the built-in browser.
Improve Claude's knowledge of common hosting workflows (Bluehost, cPanel, connecting a domain from an external registrar). It should tell users the correct order of steps and warn before destructive actions, such as deleting a site that also removes the domain.
Claude should say clearly and early when it cannot complete a task, instead of retrying for a long time.
Contact: htofashion2022@gmail.com

What Should Happen?

To: Anthropic Support
Subject: Claude (Claude Code desktop app) failed to deploy my website and connect my domain; hours wasted

Date of session: 5 October 2026
Product: Claude desktop app, Code tab (Claude Code), model Opus 5.5
Task: Build a Hebrew B2B wholesale website, upload it to my Bluehost hosting, and connect my domain bigdayavoda.com (registered at Namecheap).

Summary
Claude built the site content: a static HTML catalog and later a WordPress/WooCommerce store with 3,822 products. But it could not complete the deployment or the domain connection. The process took many hours, needed constant manual help from me, and ended with me hiring a human developer. Some failures were in the tools Claude uses; others were Claude's own mistakes or missing knowledge.

Part A – Tool / platform failures

Built-in browser stops working when the window is not in front. When the Claude window was minimized or behind another window, pages stopped rendering. Screenshots and clicks timed out. I had to keep the Claude window in the foreground for every step, and Claude repeatedly asked me to do so.
The Claude in Chrome extension could not read any page. It was connected to my Chrome, but every screenshot, page-text read or page action on Bluehost, cPanel and Namecheap failed with "script injection timed out". The same pages worked normally for me.
Bluehost single sign-on never loaded in the built-in browser. cPanel, "Edit Site" and the WordPress installer go through a Bluehost login page (nfhostingapp.com). It stayed on "Loading..." indefinitely in Claude's browser.
New tabs and popups opened by websites were blocked. Bluehost's cPanel button, the WordPress installer and the domain-connection authorization (Entri → Namecheap login popup) all open new tabs or windows. Claude's browser blocked them, so I had to click them myself.
Claude could not upload files from my computer. The built-in browser cannot use a file picker. I had to upload index.html to cPanel and choose the CSV file for the WooCommerce import myself.
Typing into a third-party chat did not work. Claude opened Bluehost's live-agent chat, but the text it typed into the chat box (a cross-origin iframe) never registered, so it could not talk to support for me.
Viewport and scaling kept changing. The browser pane changed size and zoom between screenshots, so click coordinates were wrong several times.
Part B – Claude's own mistakes and missing knowledge

Wrong order of steps for the domain. It told me to create the domain in cPanel before changing the nameservers at Namecheap. cPanel rejected it ("domain points to an IP that does not use the DNS servers associated with this server").
Wrong assumption about Bluehost's tools. It told me to install WordPress through "Softaculous" in cPanel. Bluehost's cPanel does not have Softaculous, so I searched for nothing.
Duplicate WordPress installs. Repeated clicks on Bluehost's "Add Website" during slow loading created three WordPress sites instead of one. Two empty "Welcome" sites are still in my account.
Deleting the old site removed the domain. Claude had me delete the old "Other CMS" site that held bigdayavoda.com. This also removed the domain from Bluehost's domain list. After that, the "Connect Domain" wizard showed "Not available to be connected", and Claude did not know how to fix it.
Manual DNS edits did not take effect. Claude edited the A records in Bluehost's DNS panel to point to my server IP. Bluehost's nameservers still served the old parking IP more than an hour later. Claude could not explain why.
Data import bug. Category names containing commas were split into separate categories by the WooCommerce importer, giving 88 categories instead of 47. Claude fixed it afterwards, but it should have escaped the commas in the CSV beforehand.
Guessing instead of knowing. It tried a password reset with an email that turned out not to be the WordPress admin email. It also guessed several Bluehost page URLs that returned errors (502 / 404).
Too many retries and too much waiting. It retried failing browser actions many times before telling me plainly that it could not do the task.
It ran a multi-agent research workflow without asking me first. It disclosed this afterwards.
Part C – Result

The site content is complete. WordPress/WooCommerce is installed with 3,822 products, the homepage, WhatsApp and quote buttons, and quote emails to my address.
The domain bigdayavoda.com is still not connected to the site. The site is not live, and the "Coming Soon" page is still active.
I had to hire a human developer to finish the job.
Requests

Make the built-in browser keep working when the app is in the background.
Fix the Chrome extension so it can read and control pages the user is signed in to.
Allow popups and new tabs for sign-in flows the user starts (SSO, OAuth, domain-connection services).
Allow file uploads from the session's own folders in the built-in browser.
Improve Claude's knowledge of common hosting workflows (Bluehost, cPanel, connecting a domain from an external registrar). It should tell users the correct order of steps and warn before destructive actions, such as deleting a site that also removes the domain.
Claude should say clearly and early when it cannot complete a task, instead of retrying for a long time.
Contact: htofashion2022@gmail.com

Error Messages/Logs

Steps to Reproduce

To: Anthropic Support
Subject: Claude (Claude Code desktop app) failed to deploy my website and connect my domain; hours wasted

Date of session: 5 October 2026
Product: Claude desktop app, Code tab (Claude Code), model Opus 5.5
Task: Build a Hebrew B2B wholesale website, upload it to my Bluehost hosting, and connect my domain bigdayavoda.com (registered at Namecheap).

Summary
Claude built the site content: a static HTML catalog and later a WordPress/WooCommerce store with 3,822 products. But it could not complete the deployment or the domain connection. The process took many hours, needed constant manual help from me, and ended with me hiring a human developer. Some failures were in the tools Claude uses; others were Claude's own mistakes or missing knowledge.

Part A – Tool / platform failures

Built-in browser stops working when the window is not in front. When the Claude window was minimized or behind another window, pages stopped rendering. Screenshots and clicks timed out. I had to keep the Claude window in the foreground for every step, and Claude repeatedly asked me to do so.
The Claude in Chrome extension could not read any page. It was connected to my Chrome, but every screenshot, page-text read or page action on Bluehost, cPanel and Namecheap failed with "script injection timed out". The same pages worked normally for me.
Bluehost single sign-on never loaded in the built-in browser. cPanel, "Edit Site" and the WordPress installer go through a Bluehost login page (nfhostingapp.com). It stayed on "Loading..." indefinitely in Claude's browser.
New tabs and popups opened by websites were blocked. Bluehost's cPanel button, the WordPress installer and the domain-connection authorization (Entri → Namecheap login popup) all open new tabs or windows. Claude's browser blocked them, so I had to click them myself.
Claude could not upload files from my computer. The built-in browser cannot use a file picker. I had to upload index.html to cPanel and choose the CSV file for the WooCommerce import myself.
Typing into a third-party chat did not work. Claude opened Bluehost's live-agent chat, but the text it typed into the chat box (a cross-origin iframe) never registered, so it could not talk to support for me.
Viewport and scaling kept changing. The browser pane changed size and zoom between screenshots, so click coordinates were wrong several times.
Part B – Claude's own mistakes and missing knowledge

Wrong order of steps for the domain. It told me to create the domain in cPanel before changing the nameservers at Namecheap. cPanel rejected it ("domain points to an IP that does not use the DNS servers associated with this server").
Wrong assumption about Bluehost's tools. It told me to install WordPress through "Softaculous" in cPanel. Bluehost's cPanel does not have Softaculous, so I searched for nothing.
Duplicate WordPress installs. Repeated clicks on Bluehost's "Add Website" during slow loading created three WordPress sites instead of one. Two empty "Welcome" sites are still in my account.
Deleting the old site removed the domain. Claude had me delete the old "Other CMS" site that held bigdayavoda.com. This also removed the domain from Bluehost's domain list. After that, the "Connect Domain" wizard showed "Not available to be connected", and Claude did not know how to fix it.
Manual DNS edits did not take effect. Claude edited the A records in Bluehost's DNS panel to point to my server IP. Bluehost's nameservers still served the old parking IP more than an hour later. Claude could not explain why.
Data import bug. Category names containing commas were split into separate categories by the WooCommerce importer, giving 88 categories instead of 47. Claude fixed it afterwards, but it should have escaped the commas in the CSV beforehand.
Guessing instead of knowing. It tried a password reset with an email that turned out not to be the WordPress admin email. It also guessed several Bluehost page URLs that returned errors (502 / 404).
Too many retries and too much waiting. It retried failing browser actions many times before telling me plainly that it could not do the task.
It ran a multi-agent research workflow without asking me first. It disclosed this afterwards.
Part C – Result

The site content is complete. WordPress/WooCommerce is installed with 3,822 products, the homepage, WhatsApp and quote buttons, and quote emails to my address.
The domain bigdayavoda.com is still not connected to the site. The site is not live, and the "Coming Soon" page is still active.
I had to hire a human developer to finish the job.
Requests

Make the built-in browser keep working when the app is in the background.
Fix the Chrome extension so it can read and control pages the user is signed in to.
Allow popups and new tabs for sign-in flows the user starts (SSO, OAuth, domain-connection services).
Allow file uploads from the session's own folders in the built-in browser.
Improve Claude's knowledge of common hosting workflows (Bluehost, cPanel, connecting a domain from an external registrar). It should tell users the correct order of steps and warn before destructive actions, such as deleting a site that also removes the domain.
Claude should say clearly and early when it cannot complete a task, instead of retrying for a long time.
Contact: htofashion2022@gmail.com

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

5.5

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_