Text Parse Tokens

WAS Node Suite has its own small token language - bracketed placeholders like [time], [hostname], [cuda_device], and [cuda_name] - that Save Text File and Save Image already understand natively when you're building a filename pattern. This node exists for everywhere else: it takes a string containing that token syntax and substitutes every token with its live value, wherever in your graph you happen to need it, not just in a filename field.

What it's for

Anywhere you want a dynamic value baked into text that isn't already a token-aware save node. A caption overlay that stamps the render timestamp and which GPU produced it. A filename string you're constructing by hand before handing it to a node that isn't natively token-aware. A log line you're writing with Save Text File that needs the hostname of the machine that generated it, useful if you're running distributed across more than one box.

The built-in tokens per the README:

• [time] - current system microtime, raw.
• [time(format_code)] - the current time, human-readable, using standard strftime-style formatting. [time(%Y-%m-%d__%I-%M%p)] gives you something like 2026-08-03__07-54PM instead of raw microtime.
• [hostname] - the hostname of the machine running ComfyUI.
• [cuda_device] / [cuda_name] - the active CUDA device and its name, pulled straight from ComfyUI's own device-management calls.

You can also register your own custom tokens with WAS's Text Add Tokens or Text Add Token by Input nodes, and this node will substitute those too, alongside the built-ins.

How it works

Feed it a string containing token syntax; it hands back the same string with every token replaced by its current value. One input, one output, both plain text.

It's worth noting the overlap with Save Image and Save Text File: those two nodes already parse the same token syntax internally when you use it directly in their filename fields, so you don't strictly need this node just to get a timestamped or hostname-tagged filename on a save. Reach for Text Parse Tokens specifically when you need the substituted result to go somewhere other than a filename - a caption, a log string, a piece of text you're concatenating into a longer message elsewhere in the graph.

Installing it

Part of the full WAS Node Suite pack:

• ComfyUI Manager - search WAS Node Suite, install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/WASasquatch/was-node-suite-comfyui/, then pip install -r requirements.txt from inside that folder, then restart ComfyUI.

Common issues

Token names can't contain a colon - that character is the delimiter the parser uses, so a custom token name with one in it will break. And [cuda_device] / [cuda_name] only report something meaningful if you're actually running on a CUDA GPU; on a CPU-only setup, expect those tokens to come back empty or unhelpful rather than throwing an error.

And the pack-wide caveat: WAS Node Suite has been unmaintained since December 2023, with "Import Failed" errors after a ComfyUI update a real, recurring complaint tied to older pinned dependencies colliding with newer ones. Reinstalling requirements.txt inside your ComfyUI venv is the usual fix if the whole suite stops loading.