codeloop_capture_screenshot
Capture a screenshot of the running app window (or a Playwright/Browser scene) and save it as a verification artifact.
When to use codeloop_capture_screenshot
Before any visual review or design comparison. Captures the running app to a stable artifact path so the next tool can consume it.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| screen_name | string | yes | Logical screen name (becomes the filename). |
| app_name | string | no | Window / app name to focus before capture. |
| project_dir | string | no | Project root. |
What you get back
Path to PNG screenshot, plus run_id binding.
Typical prompts that trigger it
Cursor + Claude Code call codeloop_capture_screenshot automatically when your prompt looks like one of these:
- “Capture a screenshot of the running app.”
- “Take a screenshot at /pricing for the dev report.”
FAQ
What does codeloop_capture_screenshot do?
Capture a screenshot of the running app window (or a Playwright/Browser scene) and save it as a verification artifact.
When should an AI agent call codeloop_capture_screenshot?
Before any visual review or design comparison. Captures the running app to a stable artifact path so the next tool can consume it.
What does codeloop_capture_screenshot return?
Path to PNG screenshot, plus run_id binding.
Is codeloop_capture_screenshot part of the CodeLoop MCP server?
Yes. CodeLoop ships as an MCP server installed via `npx codeloop init`. Cursor and Claude Code call it automatically once the User Rule (Cursor) or CLAUDE.md (Claude Code) is in place.