[feature] CLI get_screenshot: choose the output path #6

Closed
opened 2026-10-17 22:14:32 +00:00 by masi · 1 comment
Owner

Context: papercraft-cli call get_screenshot in a shell.
Expected: a way to choose where the PNG goes.
Actual: it always writes get_screenshot.png into the current working directory, so two consecutive calls overwrite each other and parallel agents in the same directory collide.
Repro: papercraft-cli call get_screenshot '{"nodeId":"<a>"}' then again with <b>; only the second file remains.
Workaround: run each call in a temp directory and move the file (see scripts/pc-shot.sh in skills-papercraft).
Impact: scripted comparisons and multi-agent design reviews. Suggest an out argument or an --out flag.

**Context:** `papercraft-cli call get_screenshot` in a shell. **Expected:** a way to choose where the PNG goes. **Actual:** it always writes `get_screenshot.png` into the current working directory, so two consecutive calls overwrite each other and parallel agents in the same directory collide. **Repro:** `papercraft-cli call get_screenshot '{"nodeId":"<a>"}'` then again with `<b>`; only the second file remains. **Workaround:** run each call in a temp directory and move the file (see `scripts/pc-shot.sh` in skills-papercraft). **Impact:** scripted comparisons and multi-agent design reviews. Suggest an `out` argument or an `--out` flag.
Author
Owner

Fixed in commit 5169fe6 and released in v0.3.1.

Fixed in commit 5169fe6 and released in v0.3.1.
masi closed this issue 2026-10-17 23:04:59 +00:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: masi/papercraft#6