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, absolute path, filename, type, size and known duration for every file. Select individual files, not folders; replace any file the CLI reports as unsupported.

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

Keep the returned Asset IDs and ask Codex to check them for the intended model. If that model needs further processing, query the same IDs; do not upload duplicates.

If a batch stops

ResultWhat it meansNext action
uploadedThese files received Asset IDs.Check these same IDs for the intended model.
failed or unknownOne file failed, or the network result is uncertain.Keep its ID/details and query first; do not reupload blindly.
not attemptedLater files were intentionally not started.Fix the first problem, then prepare a new plan only for files still needed.

Check availability for the model you will use

  • An Asset ID confirms that the upload was registered; it does not guarantee the file can be used by every model. Tell Codex which model will consume it.
  • Seedance still requires review approval: keep checking the same Asset ID while review is pending, and follow the reason if it fails. Kling and MiniMax do not need that review to pass; ask Codex to estimate for the target model even if review is pending or failed.
  • An asset that is being deleted cannot be used by any model. Choose another existing asset.
  • File size, duration and reference-count limits vary by model. If the estimate says file information is still processing, wait on the same Asset ID. If it reports a definite failure, follow the reason before changing or replacing the file.

I want to upload from the terminal

Show optional upload commands

The interactive command previews the files and asks once. Replace ASSET_ID with the returned ID and use the actual model name; the example checks Kling 4.0.

macOS / Linux

holycrab assets upload /absolute/path/front.jpg /absolute/path/motion.mp4

Windows PowerShell

holycrab assets upload "C:\Users\Demo\Pictures\front.jpg" "C:\Users\Demo\Videos\motion.mp4"
holycrab assets get ASSET_ID --model kling-4.0
holycrab assets wait ASSET_ID --model kling-4.0 --timeout 600

If it did not work

  • If local validation fails, fix or replace the named file; no file in that batch was uploaded.
  • If a file is rejected, check which model rejected it and read the reason before replacing or reuploading it.
  • If the result is unknown, keep the Asset ID and query it before deciding anything else.