Files

T

Claude 2040792699 Refactor to v0.2.0: context chaining, new output nodes, simplified switch

Major changes:
- PD Project Context: accepts incoming context for override chaining,
  adds auto_increment_version (persistent via widget state, like seed)
- New PD Custom Context: 5 user-defined key/value token pairs
- Replace PD Output Namer + PD Network Output with:
  - PD Output Relative (saves to ComfyUI output dir)
  - PD Output Absolute (saves to absolute/UNC paths)
  Both show a token reference panel via JS after execution
- PD Switch simplified to single-channel with auto-growing inputs (2-8)
  managed by JS extension (onConnectionsChange pattern)
- 💭 emoji prefix on all node display names (with Windows fallback)
- Consolidated all JS extensions into web/pipedream.js
- Backward compat: PDOutputNamer/PDNetworkOutput aliases preserved

https://claude.ai/code/session_015UV4rjSvFatMiNtKhd1sT3

2026-04-03 06:03:18 +00:00

3.1 KiB

Raw Permalink Blame History

ComfyUI-Pipedream

Production pipeline utility nodes for ComfyUI — output naming, network paths, shot tokens, wedge iteration, and multi-input switching.

Pipedream is not a visual effects node pack. It is plumbing.

Installation

Clone into your ComfyUI custom_nodes directory:

cd ComfyUI/custom_nodes
git clone https://github.com/theonlyaaron/comfyui-pipedream.git

No additional dependencies are required.

Nodes

All nodes appear under the Pipedream category with a 💭 prefix.

Node	Description
💭 PD Project Context	Top-level metadata node (project, sequence, shot, version, artist). Accepts an incoming context for override chaining. Supports auto-incrementing version.
💭 PD Custom Context	Adds up to 5 user-defined key/value token pairs to a context. Chain after Project Context for custom tokens like `{task}`, `{department}`.
💭 PD Shot Token	Lightweight token resolver — takes a template string and inline widget values, outputs a resolved string.
💭 PD Output Relative	Resolves a token template and saves images to ComfyUI's output directory. Shows available tokens after execution.
💭 PD Output Absolute	Same as Output Relative but saves to an absolute or UNC network path.
💭 PD Switch	Routes one of N wildcard inputs to a single output. Inputs auto-grow when connected (2–8).
💭 PD Wedge	Iteration node — holds a list of values and emits one per execution. Optional auto-queue for batch iteration.
💭 PD Rasterizer	Dry-run inspector — connects to wedges and previews the full cartesian product iteration table.

Token Reference

Tokens are {name} placeholders resolved by output nodes and PD Shot Token:

Token	Source
`{project}`	Project Context or widget
`{sequence}`	Project Context or widget
`{shot}`	Project Context or widget
`{version}`	Project Context or widget
`{artist}`	Project Context
`{date}`	Auto: YYYYMMDD
`{time}`	Auto: HHMMSS
`{frame}`	Padded frame placeholder (e.g. `####`)
`{wedge_idx}`	Current wedge iteration index
`{wedge_<name>}`	Named wedge current value
`{<custom>}`	Any key added via PD Custom Context

Context Chaining

PD Project Context accepts an optional incoming context. Non-empty widget values override the incoming values, empty widgets pass through. This lets you set up a base context and override per-shot:

PD Project Context (base: project=DITC, sequence=sq010)
    → PD Project Context (override: shot=sh010)
        → PD Custom Context (task=comp, element=BG)
            → PD Output Relative

Compatibility

Pipedream supports both the legacy ComfyUI node API and the Nodes 2.0 (V3) API. The compatibility layer detects which API is available at import time and registers nodes accordingly.

Note: Node display names use a 💭 emoji prefix. On Windows systems with legacy console codepages (cp1252, cp932), the emoji is automatically omitted to prevent encoding errors.

License

MIT — see LICENSE.

3.1 KiB Raw Permalink Blame History Unescape Escape