Google Meet runs in a browser tab. That one fact decides almost everything about whether an AI assistant can sit on your screen during an interview without the person on the other end seeing it, and most of the advice floating around gets it wrong in both directions. Some pages tell you every assistant is invisible. Others tell you Google can scan your machine. Neither is true, and the gap between them is where people get burned.
I want to walk through what Meet actually captures, what it cannot capture, and the one failure mode that no software setting protects you from. I’ve included the specific operating system calls involved, because this is a question with a real technical answer rather than a marketing answer.
What Google Meet actually sees when you share your screen
When you pick a window or a full screen in Meet, the browser asks the operating system for a capture stream. It does not read your disk, enumerate your running processes, or inspect installed applications. It receives frames. Whatever the OS compositor decides to put in those frames is what your interviewer watches, and whatever the compositor leaves out simply is not there.
That last part is the whole game. Both major desktop operating systems expose a flag that tells the compositor to omit a specific window from capture streams while still drawing it on the physical display.
On Windows it’s SetWindowDisplayAffinity with the WDA_EXCLUDEFROMCAPTURE value. On macOS it’s the NSWindow.sharingType property set to none, which ScreenCaptureKit then honors. Desktop app frameworks wrap these. Electron exposes the pair as setContentProtection(true), which is the exact call Craqly’s main process makes on the assistant window at startup.
So the honest framing is not “can Meet detect the tool”. It’s “did the tool ask the operating system to be left out of the capture, and did this particular OS version honor the request”. Those are two different questions and the second one is not fully in anyone’s control.
Does Google Meet detect an AI assistant?
No. Google Meet cannot detect software running on your computer. It has no mechanism to scan your machine, list your processes, or see applications you have not shared, and Meet’s own presentation controls only ever transmit the screen, window, or tab you explicitly select. An assistant becomes visible on Meet through one route: it appears in the pixels you chose to share.
That said, “Meet can’t detect it” is a much smaller claim than most people hear. Meet is one layer. An interview can involve several, and the others behave differently:
- A proctored coding platform running alongside the call may log tab switches, window focus changes, and paste events. Capture exclusion does nothing about any of that.
- A company-managed laptop may run endpoint monitoring that does enumerate processes. If your employer or the hiring company controls the device, assume the device reports on itself.
- A recruiter who asks you to share your entire screen rather than one window changes what the compositor is asked for, though the exclusion flag still applies per window.
Worth saying plainly: I don’t know how long the current behavior holds. Apple has tightened screen capture permissions in several recent macOS releases, and each tightening has broken capture exclusion for some apps on some hardware until they updated. Windows behavior before Windows 11 is uneven. Anyone who tells you a tool is permanently invisible is selling something.
Browser tab versus desktop app
This is the practical fork, and it’s why Meet specifically catches people out. Meet lives in Chrome. A lot of “interview copilot” products are also Chrome extensions or web apps, which puts the assistant inside the same surface you’re being asked to share.
| Assistant runs as | Can request capture exclusion | Visible if you share the whole screen | Visible if you share the Chrome tab |
|---|---|---|---|
| Chrome extension / side panel | No | Yes | Usually yes |
| Separate browser window | No | Yes | No |
| Native desktop app with exclusion set | Yes | No, on a supported OS | No |
A browser extension cannot call SetWindowDisplayAffinity. It has no access to that layer. The best it can do is live in a window you did not share, which works right up until someone asks for your full screen and then does not work at all.
The tell that has nothing to do with software
Here is what I think most of the detection discourse misses. In a Google Meet interview you are on camera, usually full frame, usually close. Your eyes are the signal.
Reading an answer off a panel produces a specific pattern: a pause, a horizontal eye track, then delivery that’s noticeably more fluent than the thinking that preceded it. Interviewers who run several calls a week notice it without being able to name it. They log it as “the answers felt rehearsed” or “couldn’t go deeper when I followed up”, and that’s what lands in the feedback form.
The follow-up question is where this actually breaks. A polished answer invites a specific probe. If you delivered a definition you read 4 seconds earlier, the probe has nothing underneath it. That gap does more damage than any screen share ever would, because it reads as a competence problem rather than a tooling problem.
Which is a long way of saying: capture exclusion solves a narrow problem well and a broad problem not at all. The tool has to support what you already know rather than substitute for it. That’s a real constraint, not a disclaimer.
The six-minute test that settles it for your machine
Don’t find this out live. The setup varies by OS version, GPU, and display configuration, and the only setup that matters is yours.
- Start a Google Meet with yourself. A solo meeting is fine.
- Join a second time from your phone, or start a recording from the desktop side.
- Open the assistant so it’s visibly on your screen.
- Share your entire screen. Not a window, the whole thing, because that’s the harder case.
- Look at the phone, or stop and replay the recording.
If the overlay shows up in the shared view, capture exclusion is not working on your machine and no amount of settings will change that today. Repeat this after every OS update, because updates are exactly when it quietly breaks. It takes about six minutes and it’s more informative than any product page, including this one.
Where Craqly sits in this
Craqly is a native desktop app on macOS and Windows rather than a browser extension, so it can make the exclusion call described above, and it does. It captures system audio through the OS loopback path, which means it hears the interviewer through Meet without joining the call as a participant and without appearing in the participant list.
Two things worth knowing before that reads as a pitch. First, stealth is on every plan including the free Starter tier, which gives you 20 credits a month and one credit is one minute of live session, so you can run the six-minute test above on your own hardware without paying anything. I’d rather you verify it than trust it. Second, most employers prohibit undisclosed AI use in interviews, and a 2025 SHRM survey found a majority of hiring managers would disqualify a candidate over it. Capture exclusion is a technical property. It is not permission, and the two get conflated constantly.
Test it on your own setup first. The free Starter plan includes 20 credits a month with stealth enabled, and one credit is one minute of live session. That is enough to run the screen share test above and see how your machine behaves before an interview depends on it.
Frequently asked questions
Can Google Meet see apps I haven’t shared?
No. Meet receives only the capture stream for the screen, window, or tab you select. It has no ability to enumerate running processes or inspect installed software. Anything outside the selected capture is not transmitted.
Will a Chrome extension interview assistant show on a Google Meet screen share?
If you share your entire screen, yes. Browser extensions cannot request capture exclusion from the operating system, because that flag is only available to native windows. An extension can only stay hidden by living in a window or tab you did not share.
Does sharing a single window instead of the full screen make an assistant safe?
It helps, but it’s fragile. Sharing one window means only that window’s frames are transmitted, so a separate assistant window stays out. The risk is that many interviewers ask you to switch to full screen partway through, and at that point only a native app with capture exclusion remains hidden.
Does an AI assistant appear in the Google Meet participant list?
Only if it joins the call as a bot. Tools that connect through the Meet API add a visible participant that everyone can see. Desktop assistants that capture system audio locally never join the meeting, so no extra participant appears.
How often does capture exclusion break?
Unpredictably, and usually after an operating system update. Apple has tightened screen recording permissions across several recent macOS versions and each change has broken window exclusion for some applications until they shipped a fix. Retest after every major update rather than assuming last month’s result still holds.