Skip to guide content

Guide

Hotkeys & stealth mode

Global hotkeys drive capture and stealth while the UI stays hidden — learn the defaults and how to adjust them.

Why hotkeys matter

In stealth mode you should not rely on clicking a floating window on the shared screen. Shortcuts let you capture, analyze, and control the app without leaving a visible trail.

Defaults (check Settings for your build)

Exact bindings can be customized in the app. A typical setup includes:

  • Capture / region capture — Grab the active problem or editor area (often something in the Ctrl+Shift family; confirm in Settings).
  • Stealth toggle — Hide or show the overlay quickly before and after a share.
  • Analysis / mode actions — Trigger analysis or switch Coding vs General mode when your build exposes those shortcuts.

Always verify bindings on your machine after install — especially on Linux, where desktop environments can reserve shortcuts.

Stealth mode habits

  1. Enable stealth before you start sharing.
  2. Work only with hotkeys and off-device delivery during the share.
  3. Only reveal the UI when the share is off or you are sure it is out of the capture region.

Settings tips

  • Open Settings when not sharing to remap conflicts with the IDE or DE.
  • Prefer shortcuts that do not clash with the browser or VS Code defaults you use daily.
  • If a shortcut never fires, see Troubleshooting and the session tip under Built for Linux.