[BUG] Claude in Chrome blocks lovable.dev in Cowork mode — regression from earlier same-day session
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?
Claude in Chrome (v1.0.68) blocks all interaction with lovable.dev — screenshot, JavaScript execution, read_page, find, and navigate all fail. This is a regression: lovable.dev was fully accessible earlier in the same Cowork session (confirmed by session transcript showing successful JavaScript injection, screenshots, and click interactions on the same domain).
What Should Happen?
lovable.dev should be accessible like any other website when the user has granted "On all sites" permission. lovable.dev was working earlier in this same session.
Error Messages/Logs
screenshot → "Permission denied for this action on this domain"
javascript_tool → "Permission denied for JavaScript execution on this domain"
read_page / find → "Permission denied for reading pages on this domain"
navigate (new tab) → "Navigation to this domain is not allowed"
Steps to Reproduce
- Open Cowork session with Claude in Chrome connected
- Navigate to any lovable.dev project URL (e.g., https://lovable.dev/projects/...)
- Attempt any browser automation tool (screenshot, javascript_tool, read_page, navigate)
- All fail with permission/domain errors
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
1.0.67
Claude Code Version
1.0.68
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
lovable.dev is a primary development tool for this project. The block prevents autonomous development workflows where Claude drives Lovable to implement, test, and deploy code changes — forcing manual copy-paste of every prompt and code change. github.com being blocked prevents filing issues, reviewing PRs, and inspecting source code.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗