SunoAIGeneratorNotSafe

Credit where it's due: the author named this node honestly. SunoAIGeneratorNotSafe is the same Suno song generator as the pack's other node, with one difference - instead of reading your session cookie from a .env file, you paste the cookie directly into a node input. That's the entire point of it, and the entire risk of it, and the name is the warning.

It exists because it's the fast path: no .env setup, no working-directory confusion, just paste and run. Every time you execute it, the node builds a fresh Suno client with the cookie string you typed, queues a generation on your account, waits for the two clips, and downloads them. For a quick "does cookie-based Suno access even still work today?" test, it's actually the more convenient of the two.

How it differs from SunoAIGenerator

Same pack (GentlemanHu/ComfyUI-SunoAI), same underlying unofficial imyzhang/suno-api wrapper, same hardcoded chirp-v3-0 model, same poll-until-ready loop, same two-songs-per-run behavior. The mechanism only diverges in one line of code: Suno(cookie=suno_cookie) instead of reading SUNO_COOKIE from the environment.

The inputs are identical to the safe variant, plus one:

• prompt - your song idea. With custom off (default), Suno writes the lyrics from this. With custom on, it becomes your lyrics.
• custom - false = "describe it and let Suno write it," true = you're providing content yourself.
• tags - style keywords, only used when custom=true and instrumental=false.
• instrumental - true for instrumental-only (and then, in custom mode, prompt acts as a style description instead of lyrics).
• filename_prefix - prefix for the saved MP3s.
• suno_cookie - the whole security story in one field. Paste the session cookie for suno.com from your browser here. Multiline, so a full cookie block fits.

Outputs are the same four strings: MP3 URL 1, MP3 URL 2, Local Path 1, Local Path 2 - the two CDN URLs and the two files saved to ComfyUI/output/suno_ai_songs/. Use the local paths downstream; CDN URLs expire.

The "not safe" part, concretely

That cookie is the credential to your Suno account, and it now lives in the node graph itself. ComfyUI saves workflow JSON with input values in plaintext, so:

• Never share a workflow that uses this node. Anyone with the JSON has your cookie. The safe node avoids this by keeping the secret in .env.
• Be aware the cookie shows up in the graph as a visible field - shoulder-surfing friendly, and it gets baked into any workflow you save.
• Same fragility as its sibling: the README banner says "API NOT WORKING ANYMORE, DON'T USE," the last commit is December 2024, and Suno rotates this kind of auth aggressively. The whole pack is a museum piece.

Install and troubleshooting

Identical to the safe node: ComfyUI Manager (search "ComfyUI Suno API"), or

cd ComfyUI/custom_nodes
git clone https://github.com/GentlemanHu/ComfyUI-SunoAI

then restart. Dependencies are just curl_cffi, python-dotenv, and typer - no models, no GPU. This variant skips the .env step entirely, which is its one advantage.

If it fails, the failure is silent: the node swallows exceptions, prints "Error generating songs" to the terminal, and returns four empty strings. No red error in the graph - check your ComfyUI console. And because a stale cookie is the usual culprit, if you get empty strings, the first thing to try is a freshly copied cookie. If that doesn't help either, you've hit the wall the README warns about: the unofficial Suno route is dead, and this node is a historical curiosity.