Assets & Images

​

get_image

• action:“get” — Fetch a generated image from ComfyUI by FILENAME and return it as an inline image. Video/audio outputs (e.g. a VHS_VideoCombine .mp4) are saved to save_dir with their original extension instead of being rendered inline. Works with remote ComfyUI instances — does not require COMFYUI_PATH. Use get_history (action:“list”) first to obtain the filename.
• action:“view” — Fetch a registered asset’s bytes by ASSET ID and return them as an inline image so the agent can see the result. Use this after a render completes (asset_id is included in the completion notification) to inspect, critique, or compare generated images. Only supports image mime types (PNG/JPEG/WebP); audio/video assets must be saved to disk via action:“get”.
• action:“list_outputs” — List recently generated image AND video files from ComfyUI’s output/ directory, newest-first, with each file’s kind (‘image’ | ‘video’), subfolder, size, and modification time. Covers stills (.png/.jpg/.jpeg/.bmp) and video/animation outputs (.mp4/.webm/.mov/.mkv/.m4v/.avi/.gif/.webp). LOCAL ComfyUI (COMFYUI_PATH set): a RECURSIVE filesystem scan of output/ — includes subfolders like video/ that VHS/SaveVideo write to, and reports size + modification time. REMOTE ComfyUI: derives the list from /history over HTTP instead (size/modified are unavailable and omitted). It does NOT return the media bytes themselves — fetch those with action:“get”. USE THIS TO CONFIRM A VIDEO RENDER (e.g. VHS_VideoCombine / LTX / WAN output) when get_history (action:“list”) shows the prompt done but lists no output: VHS-style video nodes write the file but often do NOT register in ComfyUI’s /history, so the local filesystem scan is the reliable way to verify the .mp4 exists — then chain it with upload_image (action:“stage”). THAT GUARANTEE IS LOCAL-ONLY AND INVERTS ON A REMOTE TARGET: with no disk to scan, this falls back to the very /history that omits those videos, so a REMOTE listing can neither confirm nor deny a VHS video render, and absence from it is NOT evidence the file is missing. Check a specific filename with action:“get” or upload_image (action:“stage”) instead — both read /view, straight from the output directory. Every remote result says so in its own text. Read-only.
• action:“convert” — Re-encode a generated image to PNG, JPEG, or WebP and return it inline as an image content block. Source can be a registered asset_id or a path under the local ComfyUI output directory. Optionally writes the converted image back under the output directory and reports source/output size plus bytes saved.
• action:“analyze_color” — Measure the color of a rendered image (not by eye): returns black/white points, contrast (luma std), saturation, per-channel means + cast, and clipping — plus heuristic flags (washedOut, lowContrast, liftedBlacks, dimHighlights, lowSaturation, colorCast) and a one-line verdict. Source = asset_id, a ComfyUI output ref (filename/subfolder/type), or an image path. Pass reference_path to shot-match against a known-good frame (target−reference deltas). Set histogram:true to also get an overlaid R/G/B/luma histogram PNG. Use this to diagnose ‘washed out’ objectively and decide a color fix; for a video, extract a frame to PNG first.
• action:“list_assets” — List recently generated assets, newest-first. Each call first reconciles ComfyUI’s /history, so outputs are listed even when this session did not watch the render complete (e.g. queued via panel_run, by an earlier session, or before a server restart) — those are tagged source:‘history-reconcile’, versus source:‘watched’ for renders this server saw finish. Returns count + assets (asset_id, prompt_id, filename, url, source, created_at). The registry is ephemeral and clears on server restart; records expire after COMFYUI_ASSET_TTL_HOURS (default 24h), and only the most recent completed runs are reconciled — use get_history (action:“list”) / action:“get” by filename for anything older.
• action:“asset_metadata” — Get full provenance for a registered asset including the workflow snapshot that produced it. Use this to inspect the parameters that generated an image before calling generate_image (action:“regenerate”) with overrides.

​

Parameters

​

Examples

{
  "tool": "get_image",
  "arguments": {
    "action": "list_outputs",
    "limit": 10
  }
}

{
  "tool": "get_image",
  "arguments": {
    "action": "list_outputs",
    "pattern": "fox",
    "limit": 5
  }
}

{
  "tool": "get_image",
  "arguments": {
    "action": "view",
    "asset_id": "asset_01HQ8Z3K7V"
  }
}

{
  "tool": "get_image",
  "arguments": {
    "action": "get",
    "filename": "portrait_00042_.png",
    "type": "output",
    "save_dir": "C:/Users/me/Desktop"
  }
}

{
  "tool": "get_image",
  "arguments": {
    "action": "analyze_color",
    "filename": "portrait_00042_.png"
  }
}

{
  "tool": "get_image",
  "arguments": {
    "action": "convert",
    "path": "portrait_00042_.png",
    "format": "jpeg",
    "quality": 85
  }
}

{
  "tool": "get_image",
  "arguments": {
    "action": "list_assets",
    "limit": 5
  }
}

{
  "tool": "get_image",
  "arguments": {
    "action": "asset_metadata",
    "asset_id": "asset_01HQ8Z3K7V"
  }
}

​

upload_image

• action:“image” — Upload a local image file to the connected ComfyUI’s input/ directory via the HTTP /upload/image endpoint so it can be referenced in LoadImage nodes. Works for both local and remote ComfyUI. Returns the stored filename.
• action:“video” — Upload a local video file (.mp4, .mov, .webm, .avi, .mkv, .m4v) to the connected ComfyUI’s input/ directory via the HTTP /upload/image endpoint for use in video-loading nodes such as VHS_LoadVideo (ComfyUI-VideoHelperSuite). Works for both local and remote ComfyUI. Returns the stored filename.
• action:“audio” — Upload a local audio file (.wav, .mp3, .flac, .ogg, .m4a, .aac) to the connected ComfyUI’s input/ directory via the HTTP /upload/image endpoint for use in audio-conditioned workflows (e.g. LoadAudio). Works for both local and remote ComfyUI. Returns the stored filename.
• action:“stage” — Stage an EXISTING ComfyUI output (or temp/preview) as an INPUT so the next stage’s loader (LoadImage / VHS_LoadVideo / LoadAudio) can read it. This is the CORRECT way to chain a multi-stage pipeline (e.g. Krea2 image → LTX video → WAN extend): it fetches the output’s bytes from the server via /view and re-registers them as an input via /upload/image — the same endpoints get_image and the uploads above use. Because it goes entirely through the server API, it works even when ComfyUI was launched with a CUSTOM input/output directory. Do NOT instead copy the output file or guess a filesystem input/ path — the server’s input dir may be custom and it will reject the file (“Invalid image file”), wasting the render. Pass an existing output reference ({ filename, subfolder?, type? }); the media kind (image/video/audio) is inferred from the extension unless you set kind. Returns the registered input { filename, subfolder, type: “input”, kind } — drop the returned filename straight into the loader’s image/video/audio widget.
• action:“output” — Upload a generated ComfyUI output to CLOUD storage (this is the only action that sends bytes off the machine). Source can be asset_id or a local path under COMFYUI_PATH/output. Destination can be S3, Azure Blob, HTTP PUT, or HuggingFace via the hf CLI.

​

Parameters

​

Examples

{
  "tool": "upload_image",
  "arguments": {
    "action": "image",
    "source_path": "C:/Users/me/Pictures/cat.png"
  }
}

{
  "tool": "upload_image",
  "arguments": {
    "action": "stage",
    "filename": "portrait_00042_.png"
  }
}