Upload local files with Codex
Tell Codex which files to use. HolyCrab checks the files locally and shows the complete list before any upload starts.
Ask Codex to upload
1. Give Codex the file paths
Replace these examples with the absolute paths of your own files; Demo is only an example username.
Windows: C:\Users\Demo\Pictures\front.jpg and C:\Users\Demo\Videos\motion.mp4.
macOS: /Users/demo/Pictures/front.jpg and /Users/demo/Movies/motion.mp4.
Linux: /home/demo/Pictures/front.jpg and /home/demo/Videos/motion.mp4.
Tell Codex: “Use HolyCrab to prepare these two reference files for upload: [image path] and [video path]. Show the full list first and wait for my confirmation before uploading.”
2. Review the preview
Check the target, resolved absolute path, filename, detected type, size, and known duration for every file. A folder, device, FIFO, forged file type, or unsupported file stops the entire batch before network upload.
3. Confirm once
If every item is correct, approve the complete batch once. If any item is wrong, cancel and ask Codex to prepare a new preview.
4. Do not change the files
HolyCrab checks again before execution. Replacing or editing a file after preview stops the upload.
5. Wait for processing
Codex should wait on the returned Asset IDs until they are ready. An Asset ID is the file's receipt number for later requests.
If a batch stops
I want to upload from the terminal
Show optional upload commands
The interactive command shows the full preview and asks once. Do not add automatic confirmation flags in a beginner workflow.
macOS / Linux
Windows PowerShell
If it did not work
- If local validation fails, fix or replace the named file; no file in that batch was uploaded.
- If online processing fails, read the public error and do not automatically reupload.
- If the result is unknown, keep the Asset ID and query it before deciding anything else.