screenshot

Topics in the source

• Screenshot Capture
• Tool priority
• macOS permission preflight (reduce repeated prompts)
• macOS and Linux (Python helper)
• Workflow examples
• Multi-display behavior
• Linux prerequisites and selection logic
• Windows (PowerShell helper)

Follow these save-location rules every time: 1) If the user specifies a path, save there. 2) If the user asks for a screenshot without a path, save to the OS default screenshot location. 3) If Codex needs a screenshot for its own inspection, save to the temp directory. Prefer tool-specific screenshot capabilities when available (for example: a Figma MCP/skill for Figma files, or Playwright/agent-browser tools for browsers and Electron apps). Use this skill when explicitly asked, for whole-system desktop captures, or when a tool-specific capture cannot get what you need. Otherwise, treat this skill as the default for desktop apps without a better-integrated capture tool. On macOS, run the preflight helper once before window/app capture. It checks Screen Recording permission, explains why it is needed, and requests it in one place. The helpers route Swift's module cache to $TMPDIR/codex-swift-module-cache to avoid extra sandbox module-cache prompts. To avoid multiple sandbox approval prompts, combine preflight + capture in one command when possible: For Codex inspection runs, keep the output in temp: Use the bundled scripts to avoid re-deriving OS-specific commands. Run the helper fr

This is an excerpt. Refer to the complete source and its current requirements.