Sort the market into three buckets before comparing a single feature. Some copilots are Mac-first desktop apps that later grew a Windows port. Some are web apps that live in a browser tab and always will. A few ship a real Windows binary that owns a top-level window. Only that third group can ask Windows 11 to leave a window out of a screen capture, because doing so is a Win32 call on a window handle, not a preference a web page can tick.
Three shapes hiding behind one word
"Works on Windows" is not one claim. It covers at least three architectures, and they behave completely differently once a call starts.
- Mac-first desktop app with a Windows port. The product was designed against macOS APIs, and the Windows build implements the same behaviours a second time against a different operating system. Hiding a window from capture, capturing playback audio and drawing an always-on-top overlay are three separate mechanisms on each platform. Parity between the two builds is a claim the vendor makes, not something a shared codebase hands you for free.
- Browser-only web app. You sign in and the copilot renders in a tab. Nothing installs. It runs the same on Windows, macOS and a Chromebook, which sounds like an advantage until you notice that "the same" includes "equally visible in a full screen share".
- Native Windows build. An installer puts a binary on the machine, the process creates its own top-level window, and that window has a handle the operating system recognises. This is the only bucket where operating-system capture exclusion is even reachable.
The platform matrix
Each entry below reflects how the product publicly described itself on a check made on 31 August 2026. Vendors ship new platforms, drop old ones and rename tiers, so treat this as a shortlist and confirm on the vendor's own download page before paying anything.
| Tool | Bucket | What that means on a Windows 11 machine | Capture exclusion reachable? |
|---|---|---|---|
| Interview Coder | Mac-first desktop | Reported as macOS-first. Confirm a Windows installer exists before planning a round around it. | Only if the Windows build implements it separately |
| Cluely | Cross-platform desktop, macOS lineage | Listed for macOS and Windows. It grew out of Interview Coder and broadened into sales calls and meetings. | Reported as a higher-tier feature, not a baseline one |
| Verve AI | Mac-first desktop | Reported to run on macOS. Check the download page rather than the marketing page for a Windows binary. | Unverified on Windows |
| Parakeet AI | Browser-only web app | Runs in a tab on any operating system. No install, and no window of its own. | No. A page cannot be excluded by Windows |
| Huru | Browser and mobile, rehearsal category | Timed mock questions and delivery scoring before the call, not a live overlay inside it. | Not applicable, there is no in-call overlay to hide |
| Final Round AI | Web suite with a desktop client | A broad preparation product, mock interviews and coaching, with a copilot attached. | Not the core positioning |
| LockedIn AI | Cross-platform desktop | Listed for macOS and Windows, so a genuine Windows binary exists. | Reported on supported plans |
| OfferPilot AI | Windows-only native | Windows 10 and 11 and nothing else. No macOS, no Linux, no mobile, no browser extension. | Yes, on every plan including the free one |
What capture exclusion needs, and why a tab can never have it
This is the technical fact that splits the matrix, so it is worth stating precisely rather than gesturing at it.
On Windows, a process calls SetWindowDisplayAffinity on a window handle it owns and passes the flag WDA_EXCLUDEFROMCAPTURE, which arrived in Windows 10 version 2004. The Desktop Window Manager then keeps compositing that window onto your physical monitor while omitting it from the frames handed to anything capturing the screen. The result is absence, not censorship. No black rectangle, no blur, because those pixels never enter the stream that Zoom, Teams, Meet, OBS or the Print Screen path receives. The older flag, WDA_MONITOR, produced a black box instead, which is exactly the artefact people report from tools built before the newer flag existed.
Three preconditions come with that call. Each one is a wall for a web app.
- You need a top-level window handle. A browser tab has none of its own. The only handle in play belongs to the browser frame, and your page is one rectangle drawn inside it, alongside every other tab.
- The calling process must own that window. Page JavaScript runs in a sandboxed renderer with no route to Win32. There is no web API exposing display affinity and no permission prompt that would grant it, because the capability does not exist in the platform.
- Exclusion applies to the whole window. Even if a page could reach the browser frame, excluding it would remove the entire browser, including the meeting or the coding pad you are supposed to be sharing.
A browser extension does not escape this either, and the failure is worth knowing because extensions get sold as the cross-platform answer. A side panel is drawn inside the browser window, so a window share carries it. A panel injected into the page is page content, so a tab share carries it too. Dragging an overlay to a second monitor or a second virtual desktop is also not the same mechanism, since a full screen share of the wrong display, or a plain screenshot, puts it right back into view.
Six minutes to verify a Windows build yourself
Do this on the machine you will interview on. Graphics drivers and capture backends differ between machines, and a vendor sentence is not evidence about your hardware.
Find the actual installer
On the download page, look for a Windows executable or installer package. A "get started" button that opens a sign-in page in your browser means you are in the web-app bucket, whatever the homepage claims.
Screenshot it
Open the overlay, press the Windows key with Print Screen, then open the PNG that lands in Pictures under Screenshots. If the overlay is in that file, nothing further down this list will save you.
Record ten seconds
Windows key, Alt and R starts a capture. Play the saved file back afterwards instead of trusting the live preview, because preview and encoded output do not always travel the same path.
Share your whole screen to your own phone
Start a meeting alone, join it from your phone with the microphone muted, and share your entire desktop. The phone shows exactly what a viewer receives. Your own monitor never does.
Watch the taskbar and Alt-Tab
A window being absent from the frame says nothing about its taskbar button or its Alt-Tab thumbnail. Switch windows several times while you watch the phone rather than the desk.
Put headphones on
Play a talking-head video and see whether the transcript keeps moving. A tool taking Windows playback loopback hears it either way. A microphone-only tool goes deaf the moment sound stops entering the room, which is every interview where you wear headphones.
Step six is the one that separates two products with identical feature lists. Loopback capture and microphone capture are different code paths on Windows, and only one of them survives a pair of AirPods.
Where a Windows-only tool is the wrong answer
OfferPilot AI is the Windows-only row in that table, and the limitation is not a footnote. There is no macOS build, no Linux build, no mobile app and no browser extension. If you interview on a MacBook, no feature comparison on this page helps, because the installer will not run, and a cross-platform desktop tool or a web app is your only route. That does not change with a plan upgrade.
The second limit matters more, and it applies to every row in the matrix. Capture exclusion covers screen sharing, screen recording and screenshots. That is the whole scope. It does nothing about a webcam pointed at your face, a lockdown browser inspecting running processes, an interviewer or invigilator watching you in person, eye tracking, or a phone propped up as a second camera. Eyes moving to a corner of the screen read as eyes moving to a corner of the screen, whatever is in the video frame. Where an assessment's rules forbid outside assistance, the honest advice is to close everything and sit it, and nothing in the table above changes those rules. What this category is built for is preparation, live support in a conversational interview, and accessibility for people who need help parsing a fast question or an unfamiliar accent.
How to choose, in one paragraph
If you are not on Windows, the matrix answers your question by elimination and the rest is a feature comparison you can run at leisure. If you are on Windows 11 and what you actually care about is an assist that stays out of a share, ignore the marketing copy and look for exactly two properties: a real installer, and an overlay that survives the six-minute test with headphones plugged in. Everything else, model quality, question banks, pricing units, session caps, is a preference you can revise later. Those two are architecture, and no browser tab has ever had either. Run the check on a free tier before you pay for a monthly one, and run it on a Tuesday rather than four minutes before a panel.