Sam asked whether disappearing Chrome windows could be getting accidentally dragged into a coding app or similar, making them invisible. I performed a read-only AppleScript check against macOS and Google Chrome. Chrome was running with 3 windows: Sam's Operations Center at bounds 22,22,1302,742; New Incognito Tab at bounds 0,0,1280,600; and Sign in - Google Accounts at bounds 0,0,1280,600.
The literal theory is unlikely: a normal macOS coding app cannot absorb an existing Chrome window. Chrome windows remain owned by the Chrome process. A nearby version does make sense: Spaces, Stage Manager, full-screen app groups, hidden windows, stacked windows, or external-monitor coordinate behavior can make Chrome look like it disappeared or got pulled behind another app.
Read-only Chrome window count and bounds were checked from the shell. No windows were moved, closed, or modified.
Question answered and a lightweight diagnostic record was captured. No live desktop changes were made.
A future agent can safely run a non-destructive Chrome window recovery script if Sam chooses that path: activate Chrome, bring all Chrome windows to the current desktop if macOS allows it, and tile or cascade them within the visible display bounds. If the issue repeats, inspect Mission Control, Stage Manager settings, display arrangement, and any automation or window manager that may move windows.
The useful clue is that Chrome windows existed at the time of the check. Treat future reports as a visibility/window-management issue before assuming Chrome crashed or tabs were lost.