Relay in ComfyUI — Concept Prototype

How the Code becomes fields

A relay's content stays normal markdown — no backend change needed. A tagged-on ```relay-fields fenced JSON block carries the structured params (prompt, steps, cfg, seed) alongside the human-readable body. Relay In fetches the Code and splits the two apart; Relay Field nodes pull one named key out, typed to match what the graph needs (STRING / INT / FLOAT).

Status

Prototype ships in relay-platform/clients/comfyui-relay-nodes — 4 node types, 14 passing tests, zero backend dependency. Productionizing it against a real integration-payload registry (so the fence-block convention becomes a validated schema) is tracked as Linear RCTX-827, under epic RCTX-823.

Relay In

code

HAVVPX

content

fields_json

Relay Field (String)

fields_json

key

positive_prompt

STRING

Relay Field (Int)

fields_json

key

steps

INT

Relay Field (Float)

fields_json

key

cfg

FLOAT

Show Text

text

raw relay content, for reference

CLIP Text Encode (Prompt)

clip

text

CONDITIONING

KSampler

model

positive

negative

latent_image

steps

cfg

LATENT

not yet

Save Image

images

pushing this back into a relay needs binary/object relay support — parked, RCTX-829

Why this belongs in Apps

ComfyUI is a real place work happens outside chat — this is the same "everywhere Relay shows up" pattern as Slack and Chat, applied to a node-based tool instead of a conversational one. The Code is still the unit; only the receiving surface changes.

In, not yet out

Text and parameters flow in cleanly today. Getting a generated image back out into a relay is deliberately out of scope here — Relay's content is text-only, so there's nowhere for the bytes to land except an externally-hosted URL. Tracked separately, not bundled into this concept.

Scope

Concept card only — the diagram mirrors the real node package's actual inputs/outputs, not an artist's impression. See relay-platform/clients/comfyui-relay-nodes/README.md for install + the exact convention, and the Plugin & Integration Payload Registry Linear project for what comes next.