Why doesn't Cluely show up when a candidate shares their screen during an interview?
TL;DR: Cluely and similar "invisible" AI copilots use built-in operating system APIs — macOS's ScreenCaptureKit app-exclusion filter and Windows' SetWindowDisplayAffinity (WDA_EXCLUDEFROMCAPTURE) — to tell the OS "don't include my window in any screen recording or screen share." The candidate sees the overlay; the interviewer's screen share shows a clean desktop. Catching it requires full-screen lockdown capture or behavior-based signals, not a normal Zoom/Teams screen share.
By Pinal Dave Last updated: 2026-08-02
The claim
Interviewers keep asking a version of the same question after a candidate "aced" a coding round: how did an AI overlay stay invisible on a screen that was supposedly fully shared? The answer isn't a Zoom bug — it's a deliberate, documented OS feature that Cluely, Interview Coder, and Final Round AI's "Stealth Mode" all lean on.
The evidence
Apple's own ScreenCaptureKit documentation shows developers can build a capture filter that excludes specific applications by bundle identifier (SCContentFilter(display:excludingApplications:exceptingWindows:)). Windows exposes the equivalent through SetWindowDisplayAffinity, which any app can call on its own window to mark itself invisible to screen capture, recording, and remote-desktop tools. Neither API requires admin rights or jailbreaking — it's a legitimate privacy feature (originally meant to hide password managers or DRM video) that stealth interview tools repurpose.
Reddit threads corroborate this from the candidate side. In r/leetcode's "PSA: Interview Coder, Cluely, Final Round AI, etc are 100% detectable" thread, users debate exactly this — whether a tool "shows up on screen share or [only triggers] hot key detection." In r/Cluely, one user notes a "free, native Windows app that lets you hide windows from any screen share," describing the same exclusion mechanism in plain language. Threads in r/Cluely ("Cluely visible on MS Teams Desktop App") also show the arms race is live: some conferencing apps' own capture pipelines occasionally do render excluded windows, which is why detection results are inconsistent and vendor-dependent.
Why a normal screen share can't catch this
| What the interviewer sees | What's actually happening |
|---|---|
| Zoom/Teams screen share of candidate's full desktop | OS-level API told the capture pipeline to skip the cheating tool's window |
| Candidate typing normally, eyes on screen | Overlay renders on top of the candidate's real display, invisible only to the captured stream |
| No suspicious tab switches | Tool runs as a floating always-on-top window, not a browser tab |
| Clean recording afterward | The recording pipeline uses the same excluded capture, so post-hoc review shows nothing either |
Step-by-step: how to actually check
- Ask for a true full-screen share, not a single window or tab — this closes off some browser-based tools but not OS-level overlay apps.
- Have the candidate open Activity Monitor (Mac) or Task Manager (Windows) and read out running processes; stealth tools often disguise their process name, but an unfamiliar helper process is a flag.
- Check for the macOS "Screen & System Audio Recording" permission list in System Settings > Privacy & Security — apps that request capture-exclusion permissions sometimes appear here even if invisible in the share itself.
- Use a lockdown browser or dedicated interview-proctoring layer (like Neuroxa's Browser Proctoring or AI Meeting Proctor) that captures at the display/driver level and cross-references gaze, timing, and audio — not just the app-level screen share Zoom or Teams natively offers.
- Watch behavior, not just pixels. Verbatim answers, unnatural pacing, eyes drifting to a fixed off-screen point, and zero "thinking aloud" are the tells that survive even when the screen looks clean — this is exactly what AI trust scoring is built to catch.
Why this matters now
Fabric's analysis of 19,368 interviews (July 2025–January 2026) found 38.5% of candidates flagged for AI-cheating behavior overall, rising to 48% in software engineering roles — and 61% of those flagged candidates scored above the passing threshold anyway. A tool that's invisible to a plain screen share is precisely why a pure "watch the screen" strategy misses so many cases; it's the behavioral and audio layers that close the gap.
FAQ
Does turning off screen share entirely stop Cluely? No — Cluely and similar tools also work off system audio, listening to the interviewer's question through the microphone and displaying answers on the candidate's own screen, so disabling screen share only removes one detection avenue, not the tool itself.
Can Zoom or Teams patch this so excluded windows always show? Conferencing vendors have shipped partial fixes (some users report Cluely becoming visible on the Teams desktop app in specific versions), but because the exclusion is an OS-level API, it's a moving target that shifts with every app and OS update.
Is using an exclusion API illegal? No — the API itself is a standard, documented OS feature. Using it to conceal cheating during a job interview isn't illegal, but most employers treat undisclosed AI assistance as grounds for rejection or offer rescission under their interview integrity policy.
Does Neuroxa detect capture-excluded overlay tools? Neuroxa's Browser Proctoring locks down the test environment at the browser/OS level rather than relying on a conferencing app's screen share, and its AI Meeting Proctor layers gaze tracking, audio analysis, and trust scoring on top — so detection doesn't depend on the overlay being visible in a captured frame.