Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > bv_nodepack

ComfyUI Extension: bv_nodepack

Repo Name

bv_nodepack

Author
blackvortexai (Account age: 829 days)
Nodes
View all nodes(1)
Latest Updated
2026-09-13
Github Stars
0.01K

How to Install bv_nodepack

Install this extension via the ComfyUI Manager by searching for bv_nodepack
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter bv_nodepack in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

bv_nodepack Description

bv_nodepack adds ComfyUI nodes for region-specific prompts and LoRA routing, plus structured prompts, Smart Pipes, text assistance, and stage controls to organize and reuse complex image workflows.

bv_nodepack Introduction

BV Node Pack banner

bv_nodepack adds creative and workflow-management tools to ComfyUI. Its main focus is regional prompting: giving different parts of an image their own instructions. It also includes tools for routing LoRAs to regions, refining image details in stages, working with text prompts, organizing complex node graphs, and making reusable workflows behave more predictably.

If you create scenes with several characters or objects, regional tools can help you keep their instructions separate. If your ComfyUI canvas has become difficult to navigate, Smart Pipes, structured prompts, workflow controls, and Subgraph interface tools can help you organize it. BV Text offers optional writing assistance when you want to translate or refine a prompt before using it.

How bv_nodepack Works

ComfyUI workflows pass information between connected nodes. bv_nodepack adds nodes and visual controls that let you decide what information is passed, where it applies, and when it is used.

  • Regions act like labeled areas of a composition. You can define an area for a character, give it a prompt, and assign it a stable identity. Regional V3 then prepares those instructions for supported image-generation paths. For example, a scene with two characters can have separate regional instructions rather than relying on one prompt to describe both.
  • LoRA routing associates resources with the intended region. Instead of treating every LoRA as a workflow-wide choice, Regional V3 supports independently resolved, workflow-local LoRA resources.
  • Smart Pipes carry related workflow information together. Think of them as organized routes through a busy canvas: they can move typed workflow state through connected or wireless branches while keeping connection slots stable.
  • Structured prompts keep prompt parts identifiable. Rather than editing a long sentence through fragile text replacement, you can encode meaningful prompt blocks, filter or route them, and decode them where needed.
  • Workflow controls switch stages deliberately. Named stages can be active, muted, or bypassed, making it easier to reuse a workflow with different parts enabled.
  • BV Text keeps writing assistance separate from generation. Its text field outputs the text currently stored in the node. Translation or rewriting happens only when you click a writing-assistance control—not when you queue the workflow.

These tools organize instructions and workflow state; the final image still depends on the rest of your ComfyUI workflow and the generation models you use.

bv_nodepack Features

Regional prompting and regional LoRA routing

Regional V3 Editor with layered character and interaction regions

The Regional V3 Editor lets you create named regions with layered shapes, individual prompts, and stable identities. You can use these regions to plan which instructions belong to different characters, objects, or interactions. The regions can be compiled through native conditioning or supported model-specific attention backends.

Regional V3 also supports workflow-local LoRA resources that are resolved independently. This is useful when different parts of a composition need different LoRA choices rather than a single shared stack.

For setup details and supported connections, see the Regional V3 guide.

BV Text and optional writing assistance

BV Text is a standalone node with a multiline writing field and a STRING output. You do not need a Regional document to use it. Write or paste text into the field, then connect its output wherever your workflow needs that text.

Controls below the field let you choose a configured provider and model, translate or improve the wording, and undo the last replacement. Assistance runs only when you click a control. Queuing the workflow returns the stored text unchanged. If you make a newer manual edit while a response is pending, the node preserves that edit rather than overwriting it; Undo likewise avoids replacing newer work. If a text input is linked to the node, disconnect it before editing the local field with writing assistance.

Writing-assistance prompt profiles include:

  • General: A curated general-purpose writing profile.
  • Krea 2: A conservative rewriting profile adapted from Krea 2’s official prompting guidance. It aims to preserve existing scene details and quoted lettering without inventing new content.
  • Custom: An editable prompt for your own writing instructions.

Selecting a curated profile replaces the editable system prompt. An edited template is marked Customized; saved workflows keep their actual system prompt until you explicitly select or reset a profile. Provider and language choices are independent of the writing profile. Writing settings, including a style guide, are saved in the workflow properties and may travel with saved workflows and image metadata, so do not put secrets in them. Provider credentials use separate private backend storage.

LUT and LoRA libraries

LoRA library catalog

The shared BV interfaces help you choose and configure workflow-local LoRA and LUT resources. The LUT catalog has separate Stable and Experimental channels. It keeps a local working copy for offline startup, refreshes in the background, and checks downloaded files against pinned checksums. Built-in LUTs and your .cube files under ComfyUI/models/luts use the same loading and registry path.

<details> <summary>View the LUT catalog

Stable LUT catalog

Explore the LUT library guide and LoRA library guide for the available resource workflows.

Smart Pipes

Native Smart Pipe connections in the Nord theme

This is a reviewed wiring diagram, not an executed workflow.

Smart Pipes carry typed workflow state through wired or wireless branches while preserving stable slot identities. They are intended to make larger graphs easier to connect and maintain, especially when related information must travel through several stages. See the Smart Pipes guide.

Workflow Control

Workflow Control switches named workflow stages between active, muted, and bypassed states in a deterministic way. This helps when you want one reusable workflow with optional stages rather than separate copies for every variation. See the Workflow Control guide.

Structured prompts

Prompt Encode, Category Switch and Decode connections

This is a reviewed wiring diagram, not an executed workflow.

Structured prompt tools let you encode, filter, route, and decode semantic prompt blocks. For example, keeping categories of prompt information distinct can be easier to manage than repeatedly searching and replacing pieces of one long text string. See the Structured Prompt guide.

Subgraph interface tools and latent utilities

Subgraph interface tools let you add headings, dividers, spacers, and controlled choices to purpose-built Subgraphs. These visual controls can make a reusable workflow clearer to someone opening it for the first time. See the Subgraph Interface guide.

Latent utilities provide deterministic latent sizes and transformations for reusable workflows. They help you make size-related workflow behavior deliberate and repeatable. See the Latent Utilities guide.

The pack also includes BV Seed buttons, BV Text Log Writer, and BV Remote LLM Provider, which are discussed in the update and troubleshooting notes below.

bv_nodepack Models and Profiles

bv_nodepack is a node pack, not a collection of image-generation model weights. The provided documentation does not specify a list of image models bundled with it. Regional V3 works with native conditioning and supported model-specific attention backends; consult the Regional V3 guide for the appropriate connections.

The named General, Krea 2, and Custom options in BV Text are writing-assistance prompt profiles, not image models. They change the instructions used when you request a rewrite; they do not replace the image-generation model in your workflow. You choose the writing provider and model separately.

What's New with bv_nodepack

The following are the four latest version entries supplied by the author. For earlier releases, see the complete Wiki changelog.

Version 1.4.4 — 2026-09-13

  • Added BV Text with a multiline field, text output, click-to-run translation and rewriting, Undo, and General, Krea 2, and Custom writing profiles. Queuing a workflow does not silently rewrite your prompt.
  • Reused prepared MODEL/CLIP state for unchanged Krea 2 and Anima LLLite LoRA setups across repeated runs, avoiding unnecessary preparation. Changes to files, strengths, stacks, options, or patches invalidate that reuse.
  • Applied one configured time budget to each Remote LLM request, including slow connections and slowly delivered responses. A stalled request now ends at the timeout and frees the writing-assistance slot.
  • Added bounded request handling, security documentation, third-party notices, packaging checks, and release validation. These changes primarily improve predictability and document the pack’s safeguards rather than adding new canvas controls.

Version 1.4.3 — 2026-09-08

  • Fixed BV Seed action buttons that sometimes failed to respond to ordinary clicks, including when a seed was exposed on a Subgraph node.
  • Reduced the frontend bundle by loading only the JSON editor highlighting components it needs.
  • Added packaging-scan checks and made backend housekeeping changes without changing the relevant node behavior or safeguards.

Version 1.4.2 — 2026-09-08

  • Moved settings, API keys, working LUT catalogs, and caches into ComfyUI’s private System User directory, with a verified one-time migration from the previous public folder. If your server was reachable from other machines before this update, consider rotating API keys saved there.
  • Restricted management actions—such as saving API keys, installing LUTs, and changing the catalog channel—to local clients of a loopback-only ComfyUI unless the server operator explicitly allows remote management.
  • Limited LUT downloads to an approved host without redirects; tightened folder boundaries for LoRA-related files and LUT installs; and added limits for raster masks and parallel installs.
  • Removed outdated examples, fixtures, and scripts from the runtime repository.

Version 1.4.1 — 2026-09-08

  • Limited BV Text Log Writer filenames to .txt, .json, and .log.
  • Required Regional LoRA stacks and associated model-hash reads to use .safetensors files inside configured ComfyUI LoRA folders.
  • Removed the destination field from BV Remote LLM Provider. Custom provider destinations are configured through the appropriate backend settings or API-key configuration instead of being chosen by a workflow.

Troubleshooting bv_nodepack

A new node, interface change, or button fix does not appear

  1. Restart ComfyUI after updating.
  2. Hard-refresh or reload the browser so it loads the updated frontend.
  3. Reopen the workflow and check the node again.

If canvas buttons still require several clicks after the 1.4.3 BV Seed fix, you can raise ComfyUI’s Comfy.Pointer.ClickBufferTime setting from 32 to 150 ms.

An older Regional workflow has missing or confusing connections

  1. Keep a backup of the original workflow.
  2. Load it and inspect any deprecated Regional connections. Supported node-local data is migrated on load, but loading does not overwrite the saved workflow file or silently rebuild deprecated wiring.
  3. Migrate remaining legacy connections to the Regional V3 resource flow.
  4. Save the updated workflow, reload it, and run it once to check the result.

To inspect hidden legacy ports or V3 provider links, press Ctrl+Alt+B to toggle Regional Legacy Debug Mode. You can change this shortcut in ComfyUI Settings → Shortcuts. The Regional V3 guide provides further context.

A LoRA is rejected

  1. Check that the file ends in .safetensors. Regional LoRA stacks reject pickle-based .pt, .ckpt, and .bin files.
  2. Check that it is inside a configured ComfyUI LoRA folder, including any folders registered through extra_model_paths.yaml.
  3. Check that a linked file or folder does not point outside its configured folder. The same containment rule applies to previews, sidecars, and associated metadata hashes.

BV Text assistance cannot be used, or a custom provider points to the wrong destination

First, confirm that you are clicking a translation or improvement control: normal workflow execution only outputs BV Text’s stored text. If its local field cannot be edited with assistance, disconnect a linked text input.

For an OpenAI Compatible provider, open Configure API Key, confirm the destination shown there, and save the key again. For Local OpenAI Compatible (Custom), the operator can set profile_defaults.local-openai-compatible.custom_endpoint in the private remote_llm_settings.json if the catalog’s loopback destination does not fit. A workflow cannot choose its own provider destination.

If a provider times out, its response may have exceeded the configured timeout_seconds budget. The operator can adjust that setting in the private remote_llm_settings.json for a legitimate slow provider.

API-key or LUT management controls are unavailable

These management actions are restricted by the server’s configuration. They normally accept local clients when ComfyUI listens only on a loopback address. On a --listen server, remote management requires an explicit operator opt-in, which opens those actions to every client that can reach the server. Ask the person who manages your ComfyUI server rather than treating this as a workflow error.

On an older ComfyUI without the System User API, the pack does not fall back to storing sensitive files in the public folder. API-key providers and catalog updates are disabled, while other features continue to work.

A text log filename is rejected

Use a filename ending in .txt, .json, or .log. Log files and the bv_logs directory must not be links outside the ordinary log location under the configured ComfyUI output root.

Frequently asked questions

Will BV Text change my prompt when I queue the workflow?
No. It outputs the stored text unchanged. Writing assistance runs only when you click its controls.

Will loading an older Regional workflow rewrite my saved file?
No. Loading may migrate supported node-local data in memory, but you choose when to save the workflow.

Can I use my own LUT file?
Yes. Place a .cube file in the LUT folder described above. The pack does not support foreign LUT catalogs.

Where are provider keys stored?
The pack stores runtime files in ComfyUI’s private user/__bv_nodepack/ directory on supported versions. Writing settings saved in workflow properties are separate from provider credentials; do not put secrets in workflow writing instructions.

Is an imported workflow automatically safe to run?
No. Review workflows before running them, and keep ComfyUI accessible only to trusted users. See SECURITY.md for the pack’s security model.

Learn More about bv_nodepack

The BV Node Pack Wiki is the main source for detailed node guides and references. A useful path through the documentation is:

  1. Start with Regional V3 for composition-specific prompting.
  2. Explore the LoRA library and LUT library when your workflow needs those resources.
  3. Use Smart Pipes, Structured Prompts, and Workflow Control to make larger workflows easier to manage.
  4. Consult the Subgraph Interface and Latent Utilities guides when building reusable workflows.

Reviewed example workflows are planned as ComfyUI templates in example_workflows/ once they are updated for the current node set; the documentation does not present them as currently available. For release history, use the Wiki changelog.

The author notes that bv_nodepack was developed with extensive generative-AI assistance, while product direction, architecture, review, and validation in real workflows remain human-led.

bv_nodepack Related Nodes

RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

bv_nodepack detailed guide | ComfyUI