AuK Local 连接

The name makes it sound like boilerplate you drag in and forget. It isn't. AuK Local 连接 ("AuK Local Connection") is the node that talks to a speech service running outside ComfyUI, and it's the node that fails first and loudest when your setup is wrong - which is the most useful thing about it.

Audio in ComfyUI has one chronic disease, and it isn't model quality: every audio pack bolts its own transformers/torch stack into the same Python environment, which is why the TTS suites themselves admit "it can be a pain adding one new model and then breaking 3 old ones." AuK sidesteps that. AuK - Tencent's speech generation and editing model - plus Qwen2.5-Omni-3B live in a separate local service, and these two nodes are just an HTTP client. The connection node is the boundary between your graph and that service.

What it actually does

It is not a generator. It loads no model, produces no audio, and imports nothing heavy - the pack is a few hundred lines of stdlib urllib plus torchaudio. Its only real work happens when you hit Queue: it resolves the token file, builds a client, and calls GET /api/v1/health on the service. Incompatible protocol version, missing token - it stops right there, with 协议不兼容：节点 1.0，服务 … instead of something cryptic twenty seconds into a render.

Then it hands the rest of the graph a small bundle - URL, token file path, selected model, the two flags below - over one wire.

The inputs that matter

service_url - leave it at http://127.0.0.1:7860. The validation is deliberately strict: http only (not https), host must be 127.0.0.1, localhost or ::1, no username, path, query or fragment. Point it at your LAN rig or a tunnel and you get AuK Local 服务地址只能是本机 loopback HTTP 地址. The service binds loopback only. This is local-first, not cloud: no key, no bill.

token_file - the field that burns people. Every request carries an X-AuK-Token header, and the token lives in the integration package at data/session-token. Leave the field blank and the node reads a auk-local-config.json next to nodes.py, which the package's installer (安装ComfyUI节点.cmd) writes for you. If you installed via ComfyUI Manager that file doesn't exist - there was no installer - so paste the absolute path to data/session-token yourself. Otherwise: 找不到 AuK Local 服务令牌；请运行整合包里的"安装ComfyUI节点.cmd". The workflow stores only the path, never the token, so sharing a graph doesn't leak it.

model - flash or base, default flash. This is the whole graph's model choice, not a per-run one, since the generate node just reads what the connection handed it. flash is the four-step fast path; base is the quality and editing model.

cpu_offload - on by default, handled service-side. Leave it unless you have VRAM to burn. keep_loaded - off, hidden in the advanced drawer; it asks the service to keep the model in memory between tasks. Pointless for one clip, real savings on a batch of twenty.

One output: 连接, type AUK_LOCAL_CONNECTION, which plugs into AuK Local 生成 / 编辑. You can fan one connection into several generate nodes.

Install

ComfyUI Manager: search AuK Local · T8star-Aix, install, restart. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/Comfyui-Auk-T8

The clone gives you the bridge and nothing else. requirements.txt is a comment with no packages - torch and torchaudio come from ComfyUI - so there's no pip step and no way for this pack to break your environment. You do need ComfyUI >=0.3.48, since it's written against the V3 node API (io.ComfyNode, comfy_entrypoint). Grep for NODE_CLASS_MAPPINGS, find none, assume new rather than broken.

The models and the service come from the one-click integration package. 启动AuK服务.cmd starts it, and its window must stay open. Weights are mirrored at t8star/Auk-Comfy with pinned revisions and SHA-256 hashes: about 6.1 GB for the AuK checkpoint, 637 MB for the VAE, roughly 12 GB of Qwen2.5-Omni-3B. Fair warning - that package ships for Windows 10/11 x64 and the repo classifies Microsoft Windows only, so on Linux you're launching the service yourself.

Where people get burned

• Connection refused on the health call. The service isn't running, or you closed its console window. Nothing will tell you more clearly than this node.
• Token errors after a Manager install. See above. The number one reason a fresh install does nothing.
• Protocol mismatch, or no nodes in the menu. Node and service came from different package downloads; or ComfyUI is older than 0.3.48. They live under the AuK Local category with Chinese display names.

Once 连接 goes green, the interesting part starts - sixteen tasks, two text fields, and a hard 30-second ceiling. That's the piece on AuK Local 生成 / 编辑 (/node/AuKLocalGenerateEdit).