How stealth works
The client uses window capture protection and shortcut controls to reduce interference with shared views and the foreground page.
Screen-sharing stealth
- Uses operating-system window capture protection. The shared result depends on the operating system and the meeting app's capture method.
- Normal floating controls support interaction while keeping the foreground page focused. Complete system interactions, such as initial permissions, before your session.
- Keyboard protection: both Windows and macOS clients support it in Advanced Settings. Windows blocks left/right Ctrl; macOS blocks left/right Command. See keyboard protection settings.
Supported platforms and settings
The platform list below is consistent with the quick start page:
| Platform | Type | Current support | Notes |
|---|---|---|---|
| Chrome browser | Browser | Low-interference display by default | No extra setting required |
| Edge browser | Browser | Low-interference display by default | No extra setting required |
| NowCoder | Coding platform | Low-interference display by default | No extra setting required |
| CoderPad | Coding platform | Low-interference display by default | No extra setting required |
| HackerRank | Coding platform | Low-interference display by default | No extra setting required |
| Feishu | Video meeting | Low-interference display by default | No extra setting required |
| DingTalk | Video meeting | Low-interference display by default | No extra setting required |
| Google Meet | Video meeting | Low-interference display by default | No extra setting required |
| Tencent Meeting | Video meeting | Requires setting | Select "prioritize fluency" when sharing |
| Zoom | Video meeting | Requires setting | Enable "Advanced capture with window filtering" |
Tencent Meeting and Zoom setup
Follow the meeting setup steps and screenshots, then verify the shared view.
Self-check before each interview
The main site includes self-check tools, with no sign-in required. Complete the meeting settings above and keyboard protection setup, then keep the client running and verify each behavior below. Instructions and result explanations are built into each tool:
- Shared screen: select the entire screen containing the client, inspect the toolbar and panels in the preview, then stop sharing. Test an application window separately if that matches your actual sharing setup.
- Page focus: switch tabs once as a baseline and confirm a departure is recorded. Start a new round, keep the page in front and test your usual client actions.
- Keyboard events: recording starts automatically across the page, with no test-area click needed. Press A to verify recording, then compare the same shortcut and modifier side with protection off and on, and check the client action. You can stop, clear or export the log.
These checks describe this browser and this round of actions. They do not replace verification in other sites or meeting apps. Switching tools stops the active check; logs remain in the page and can be exported manually. Refreshing clears them.
If a result is unexpected, review the shared source, shortcut settings and system permissions, then check common issues.