Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] [Claude in Chrome] Claude in Chrome workflow recorder cannot capture dynamically injected second-layer modals [1 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#47119•Fetched 2026-04-13 05:40:57
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
augusto-borellaaugusto-borella
Participants
augusto-borellaaugusto-borella
Timeline (top)
labeled ×3

Error Message

Error Messages/Logs

No error message shown. The second modal simply does not appear during

Root Cause

  • OS: macOS 10.15.7, Chrome 146.0.0.0
  • The issue is likely to affect any site using stacked dynamically rendered modals (post composers, booking flows, multi-step forms), not just LinkedIn
  • Root cause hypothesis: the recorder listens to the original DOM tree and misses elements injected as new JS layers after recording starts

Code Example

No error message shown. The second modal simply does not appear during 
recording. The page continues as if the button was never clicked.
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?

When recording a workflow in Claude in Chrome, the recorder fails to capture user interactions inside modals that are dynamically injected into the DOM as a second layer on top of an existing modal.

Reproduction example: on LinkedIn, the post composer opens normally as the first modal. But when clicking "Schedule for later", the date/time picker — which LinkedIn injects dynamically as a second JS layer — is completely invisible to the recorder. The workflow gets stuck and cannot progress past that step.

What Should Happen?

The recorder should capture all modal interactions regardless of whether they are part of the original DOM or injected dynamically as a subsequent layer.

Error Messages/Logs

No error message shown. The second modal simply does not appear during 
recording. The page continues as if the button was never clicked.

Steps to Reproduce

  1. Open LinkedIn (linkedin.com) in Chrome
  2. Start recording a workflow in Claude in Chrome
  3. Click "Start a post" to open the post composer (first modal — works fine)
  4. Click the "Schedule for later" clock icon inside the composer
  5. Observe: the date/time picker modal does not open or is not captured by the recorder — workflow cannot continue

Confirmed: the LinkedIn scheduling modal works perfectly in normal Chrome usage outside of recording. This is isolated to the workflow recorder.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

N/A — issue is with Claude in Chrome workflow recorder (Cowork mode), not Claude Code CLI. Chrome version: 146.0.0.0

Claude Code Version

N/A — issue is with Claude in Chrome workflow recorder (Cowork mode), not Claude Code CLI. Chrome version: 146.0.0.0

Platform

Other

Operating System

macOS

Terminal/Shell

Other

Additional Information

  • OS: macOS 10.15.7, Chrome 146.0.0.0
  • The issue is likely to affect any site using stacked dynamically rendered modals (post composers, booking flows, multi-step forms), not just LinkedIn
  • Root cause hypothesis: the recorder listens to the original DOM tree and misses elements injected as new JS layers after recording starts

extent analysis

TL;DR

The issue can be mitigated by modifying the recorder to listen for dynamic DOM changes and capture interactions within subsequently injected modal layers.

Guidance

  • Investigate the recorder's event listening mechanism to determine if it can be modified to detect and capture dynamic DOM changes, such as the injection of new modal layers.
  • Consider implementing a recursive or iterative approach to scan the DOM for changes after the initial recording starts, to ensure that subsequently injected elements are captured.
  • Review the Chrome extension's content script injection and execution timing to ensure that the recorder is properly initialized and listening for events before the dynamic modals are injected.
  • Test the recorder with various websites that use stacked dynamically rendered modals to verify the issue's scope and potential fixes.

Example

No specific code example can be provided without more information about the recorder's implementation details.

Notes

The root cause hypothesis suggests that the recorder's limitation is due to its reliance on the original DOM tree, which may not account for dynamic changes. However, without access to the recorder's codebase, it's challenging to provide a definitive solution.

Recommendation

Apply a workaround by modifying the recorder to listen for dynamic DOM changes, as this approach addresses the suspected root cause and may provide a viable solution for capturing interactions within subsequently injected modal layers.

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…
#LLM response#prompt template#agent execution#callback error#memory management

Still need to ship something?

×6

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

Back to top recommendations

TRENDING