bc0edb1827
The Knowledge Base directory was entered in two places — the Configuration node's knowledge_base path and the Knowledge Base Loader node's path — a duplication with no benefit. Remove the Knowledge Base Loader node and have the Configuration node load the Knowledge Base itself, emitting it on a new knowledge_base output wired into the Resolver. - New nodes/kb_loading.py holds the shared, process-wide load-once cache and package-relative path resolution (extracted from the deleted loader node). - Configuration node: gains a knowledge_base_reload input and a KNOWLEDGE_BASE output; RETURN is now (config, knowledge_base, warnings, errors). A KB load failure surfaces on errors while the config is still emitted (the Analyzer and Validator do not need the KB). - Remove SceneCompilerKnowledgeBaseLoader from the node registrations. - Rebuild the example workflow to wire Configuration.knowledge_base -> Resolver. - Docs (README, docs/nodes.md) updated; tests moved to test_kb_loading.py. BREAKING CHANGE: the Knowledge Base Loader node is removed. Workflows that used it must load the Knowledge Base via the Configuration node's knowledge_base output. Co-authored-by: kunail0804 <kunail0804@gmail.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
3.4 KiB
ComfyUI node reference
The exact inputs, outputs, and data types of the shipped Scene Compiler nodes.
All nodes appear under the Scene Compiler category. Data flows between nodes
as typed objects; the inter-stage types are SCENE, RESOLVED_TAGS,
CATEGORY_MAP, KNOWLEDGE_BASE, and COMPILER_CONFIG.
Nodes are thin adapters: all behaviour lives in the compiler package, which
never imports ComfyUI.
Every stage node also exposes a raw string output — a JSON dump of that
node's data output — for inspecting the pipeline (wire it into a text/preview
node). The Knowledge Base Loader's raw summarizes the loaded entries. A
relative Knowledge Base path is resolved against the installed package, so the
default knowledge_base/ works regardless of ComfyUI's working directory.
Pipeline nodes
| Node | Inputs | Outputs |
|---|---|---|
| Scene Analyzer | natural_language (STRING), config (COMPILER_CONFIG, optional — supplies model/temperature/retries/timeout), system_prompt (STRING, optional override) |
scene (SCENE), warnings (STRING), errors (STRING) |
| Scene Validator | scene (SCENE), config (COMPILER_CONFIG, optional) |
scene (SCENE), warnings (STRING), errors (STRING) |
| Resolver | scene (SCENE), knowledge_base (KNOWLEDGE_BASE), config (COMPILER_CONFIG, optional) |
resolved_tags (RESOLVED_TAGS), warnings (STRING), errors (STRING) |
| Category Splitter | resolved_tags (RESOLVED_TAGS) |
category_map (CATEGORY_MAP), warnings (STRING), errors (STRING) |
| Prompt Builder | category_map (CATEGORY_MAP), config (COMPILER_CONFIG, optional) |
one STRING per category (character, appearance, hair, face, eyes, expression, body, clothing, accessories, pose, action, interaction, objects, environment, camera, lighting, style, quality, miscellaneous) plus reserved negative and scene (STRING) |
The Category Splitter produces the intermediate Category Map; the per-category prompt strings are produced by the Prompt Builder.
Support nodes
| Node | Inputs | Outputs |
|---|---|---|
| Configuration | one input per configuration option (analyzer, resolver, validator, prompt builder, semantic, debug), plus the Knowledge Base knowledge_base path, resolver_knowledge_base_version, and knowledge_base_reload |
config (COMPILER_CONFIG), knowledge_base (KNOWLEDGE_BASE), warnings (STRING), errors (STRING) |
| Debug Viewer | scene (SCENE, optional), resolved_tags (RESOLVED_TAGS, optional), category_map (CATEGORY_MAP, optional), warnings (STRING, optional), errors (STRING, optional) |
report (STRING) |
- The Configuration node is the single place for compiler settings. Its
configoutput feeds the optionalconfiginput of the Scene Analyzer, Validator, and Resolver, and it also loads the Knowledge Base from the configured path/version and emits it on itsknowledge_baseoutput (wired into the Resolver'sknowledge_baseinput) — so the Knowledge Base directory is entered in one place. There is no separate Knowledge Base Loader node. Bumpknowledge_base_reloadto force a fresh read (no automatic file watching). - The Debug Viewer is read-only; connect any intermediate state to inspect it.
A ready-to-use workflow wiring all of these is in
examples/workflows/scene_compiler_pipeline.json.