Test Codex image attachment temp path

REPORT-codex-image-attachment-test.md

@@ -0,0 +1,27 @@
+# Codex Image Attachment Test (Playwright MCP)
+
+## Summary
+- Image upload via the new agent screen succeeded and Codex identified the color as red.
+- The Codex prompt still appears to contain base64 image data rather than a temp file path.
+- `/tmp/paseo-attachments` was not created during the request.
+
+## Steps
+1. Opened `http://localhost:8081/agent/new` with Codex selected, working dir set to `/Users/moboudra/dev/voice-dev`.
+2. Clicked the attachment icon in the composer and uploaded `/tmp/red.png`.
+3. Sent message: `what color is this image?`.
+4. Observed agent response and timeline.
+
+## Evidence
+- UI console logs showed image attachments included in create-agent request:
+  - `handleSendMessage - selectedImages: 1`
+  - `createAgent called with images: 1`
+  - `createAgent message has images: true 1`
+- Agent response:
+  - `The image is solid red (#ff0000).`
+- Timeline showed a tool command containing inline base64 data:
+  - `/bin/zsh -lc python - <<'PY' ... b='iVBORw0K...' ...`
+- Temp directory not created:
+  - `ls -la /tmp/paseo-attachments` → `No such file or directory`.
+
+## Implication
+The Codex prompt still includes base64 data (or an equivalent inline payload) rather than referencing a temp file path, so the recent fix to write attachments under `/tmp/paseo-attachments` does not appear to be taking effect.