4.1 KiB
Upload and Approval
Upload a temporary preview for the user to review, then either promote to permanent hosting or save locally based on user choice.
Step 1: Preview Upload (Temporary)
Upload the evidence file (GIF or PNG) to litterbox for a temporary 1-hour preview:
python3 scripts/capture-demo.py preview [ARTIFACT_PATH]
The last line of output is the preview URL (e.g., https://litter.catbox.moe/abc123.gif). This URL expires after 1 hour — no cleanup needed.
For multiple files (static screenshots tier), upload each file separately.
If upload fails after retry, fall back to opening the local file with the platform file-opener (open on macOS, xdg-open on Linux) so the user can still review it. Include the local path in the destination choice question instead of a URL.
Step 2: Destination Choice
Present the preview URL to the user and ask how to handle the evidence. Use the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_user in Gemini, ask_user in Pi (requires the pi-ask-user extension). Fall back to presenting options in chat only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question.
Question: "Evidence preview (1h link): [PREVIEW_URL]. Where should the evidence go?"
Options:
- Upload to catbox (public URL) -- promote to permanent hosting for PR embedding
- Save locally -- save to a stable OS-temp path ($TMPDIR/compound-engineering/ce-demo-reel/)
- Recapture -- provide instructions on what to change
- Proceed without evidence -- set evidence to null and proceed
If the question tool is unavailable (headless/background mode), present the numbered options and wait for the user's reply before proceeding.
On "Upload to catbox (public URL)"
Proceed to Step 3: Promote to Permanent Hosting.
On "Save locally"
Proceed to Step 3b: Local Save.
On "Recapture"
Return to the tier execution step. The user's instructions guide what to change in the next capture attempt. After recapture, upload a new preview and repeat the destination choice.
On "Proceed without evidence"
Set evidence to null and proceed. The preview link expires on its own.
Step 3: Promote to Permanent Hosting
After the user selects "Upload to catbox", upload to permanent catbox hosting. The command accepts either the preview URL (preferred) or the local file path (fallback):
python3 scripts/capture-demo.py upload [PREVIEW_URL or ARTIFACT_PATH]
If Step 1 produced a preview URL, pass it here -- catbox copies directly from litterbox without re-uploading. If Step 1 fell back to local review (no preview URL), pass the local artifact path instead.
The last line of output is the permanent URL (e.g., https://files.catbox.moe/abc123.gif). Use this URL in the output, not the preview URL.
For multiple files, promote each separately.
Step 3b: Local Save
After the user selects "Save locally", save the artifact to the default OS-temp path using the pipeline script:
python3 scripts/capture-demo.py save-local --file [ARTIFACT_PATH] --branch [BRANCH_NAME]
Determine [BRANCH_NAME] from git branch --show-current or the PR context discovered in Step 0 of the SKILL.md.
The last line of output is the absolute path of the saved file. Use this path in the output.
For multiple files (static screenshots tier), save each file separately.
If save fails (permission denied, disk full), report the error and offer to retry or fall back to catbox upload (Step 3).
Step 4: Return Output
Return the structured output defined in the SKILL.md Output section: Tier, Description, and either URL (permanent catbox URL) or Path (local file path). The caller formats the evidence into the PR description. ce-demo-reel does not generate markdown.
Step 5: Cleanup
Remove the [RUN_DIR] scratch directory and all temporary files. Preserve nothing -- the evidence lives at the permanent URL or has been copied to the local save path.