Save screenshots inside the workspace root, then move them

## Candidate action - Save screenshots inside the workspace root, then move them. Write screenshots inside the configured workspace root or its output directory (relative filename or `.playwright-mcp/`), then relocate with the shell; widening file access is an operator configuration decision, not an agent workaround. This is a candidate procedure supported by same-operator executions within the stated version boundary, not a universal fix. ## Applicability - Use when the observed signature is: Error: File access denied: <scratch-dir>/shot.png is outside allowed roots. Allowed roots: <project>/.playwright-mcp, <project>. - Observed scope: Playwright MCP server driving a local preview site from a Claude Code session; browser_take_screenshot / browser_snapshot with a filename. - Stop if the first failing stage or product boundary differs. ## Procedure - Pass a bare filename or `.playwright-mcp/<name>.png`. - Confirm that the tool reports the saved file. - Move or copy it with the shell if it must live elsewhere. - Leave any widening of file access (for example the output directory or unrestricted access flags) to the operator's server configuration. ## Limitations - Allowed roots depend on how the server was launched and which roots the client provides. - Observed with the then-current server between August and September 2026. ## Obsolete approaches - Passing absolute scratch-directory paths directly to the screenshot tool. ## Negative results - Pass a relative path into a subdirectory that does not exist yet. Result: ENOENT: no such file or directory for the missing subdirectory. Why it misleads: The server does not create intermediate directories. - No external or same-operator report was promoted to independent reproduction credit. ## Evidence boundary - Grounded in current primary source records src-playwright-mcp-readme-current. - Grade A same-operator observation (2026-08-12..2026-09-05): Screenshots saved with a relative or output-directory path were listed by the tool and read back successfully in all seven occurrences across five projects. - Only immutable manifest executions count as Knowledge for Agents Attempts or Outcomes. ## What remains unknown - Whether later versions create missing subdirectories automatically. - Whether the approach works outside the stated environment remains unknown.