RTX Remix Start Context

This is the node every RTX Remix REST API workflow begins with. RTX Remix Start Context takes an address and a port and wraps them into an RTXRemixContext - a single connection object that every other REST node in the pack threads through its context input. Start Context is the head; RTX Remix End Context is the tail; everything in between hangs off the same thread.

Don't be fooled by the name into expecting a big event. The node does no API calls at all - it just packages two numbers into a token. Its real power is what the context does downstream: because every node passes the same context through, the pack uses it to enforce execution order. A node won't run until the node feeding its context has run. That's how you get deterministic sequences like "open project → get layers → ingest → set texture → save layer" instead of a free-for-all.

Inputs:

• address (STRING) - the Toolkit's host. Feed it from RTX Remix Rest API Details (default 127.0.0.1), a string constant, or your own typing.
• port (INT) - the Toolkit's REST port, default 8011.

Output:

• context (RTXRemixContext) - the connection token to thread into your first real node.

Install: part of NVIDIAGameWorks/ComfyUI-RTX-Remix. ComfyUI Manager (search "RTX Remix") or:

cd ComfyUI/custom_nodes
git clone https://github.com/NVIDIAGameWorks/ComfyUI-RTX-Remix
# restart ComfyUI

Needs ComfyUI v0.3.48+ (V3 schema). No Toolkit required for Start Context itself - it's pure config - but the workflow you hang off it absolutely needs one running.

Where people get burned: the context object is opaque in the UI, and beginners sometimes expect to inspect it or treat it like a value to use directly. You don't - you just wire it into the next node's context input and let the pack handle it. The bigger trap is not having a Start Context at all: drop a REST node on the canvas, try to wire it, and you'll find its context input has nothing to connect. This node is the missing link. And since every branch of a REST workflow carries its own context, keep one Start Context per independent chain - or branch the same context, which is fine, since all branches share the same connection anyway.