Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude in Chrome blocks lovable.dev in Cowork mode — regression from earlier same-day session [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48139•Fetched 2026-04-15 06:32:04
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
farmhand-datafarmhand-data
Participants
farmhand-datafarmhand-datagithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×6commented ×1

Error Message

Error Messages/Logs

Code Example

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"
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • 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

  1. Open Cowork session with Claude in Chrome connected
  2. Navigate to any lovable.dev project URL (e.g., https://lovable.dev/projects/...)
  3. Attempt any browser automation tool (screenshot, javascript_tool, read_page, navigate)
  4. 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.

extent analysis

TL;DR

Downgrade to Claude Code version 1.0.67 to potentially resolve the permission issues with lovable.dev.

Guidance

  • Verify that the issue is specific to version 1.0.68 by testing with the previous version (1.0.67) to confirm the regression.
  • Check the permission settings in the Claude Code configuration to ensure that "On all sites" permission is granted for lovable.dev.
  • Test other domains to see if the permission issue is specific to lovable.dev or a more general problem.
  • Consider filing a bug report with more detailed logs or error messages to help the development team investigate the issue further.

Example

No code snippet is provided as the issue seems to be related to configuration or versioning rather than code.

Notes

The issue might be related to changes in permission handling or domain access introduced in version 1.0.68. Downgrading to the previous version may provide a temporary workaround.

Recommendation

Apply workaround: Downgrade to version 1.0.67, as it is confirmed to be working in the past and the issue is identified as a regression.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#dependency conflict#environment setup#docker error#permission error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING