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 > OpenKatana > OpenKatana · List plugins

ComfyUI Node: OpenKatana · List plugins

Class Name

OpenKatana_list_plugins

Category
OpenKatana/Tools
Author
rk0neki (Account age: 235days)
Extension
OpenKatana
Latest Updated
2026-11-05
Github Stars
0.05K

How to Install OpenKatana

Install this extension via the ComfyUI Manager by searching for OpenKatana
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter OpenKatana 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

OpenKatana · List plugins Description

Lists available OpenKatana session plugins, validating manifests, assets, and compatibility.

OpenKatana · List plugins:

OpenKatana_list_plugins lets you inspect the plugin catalog available within an OpenKatana execution session, helping you check which extensions are available before relying on them in a creative workflow. It loads the configured plugins into a browser-backed environment and requests their catalog, rather than simply listing files in a folder. During this process, OpenKatana validates plugin manifests and packaged assets, checks compatibility with its plugin API, and verifies that tracked plugin files do not change while the session is running. This makes the node useful for checking plugin availability, investigating setup problems, and recording the execution environment for repeatable workflows. It is an inspection tool, not a plugin installer or an image-generation operation.

OpenKatana · List plugins Input Parameters:

project_id

A required STRING that identifies the project context passed to the OpenKatana tool call. Use the identifier associated with the project you intend to inspect, keeping it consistent with related OpenKatana operations in your workflow. The node passes this value into its argument-preparation step; the supplied code does not show how project identifiers are validated or how a project is resolved to its underlying resources. No default value, minimum or maximum length, or list of accepted identifiers is specified in the provided interface.

arguments

A required STRING containing the tool arguments processed by OpenKatana’s argument-preparation layer before the call is executed. This is the exposed place to supply tool-specific argument data, since this node has no additional typed tool fields in its listed interface. The underlying listing function operates on a root location and plugin manifests, but the supplied code does not establish how those details are represented in this string or obtained from the project context; do not assume that they are additional node inputs or invent an argument schema. Use the argument format documented by your installed OpenKatana tool definition. No default value, length limits, or accepted options are shown in the provided interface.

after

An optional STRING accepted by the node’s execution method. In the supplied implementation, this value is not explicitly read, added to the prepared arguments, or passed to the tool invocation, so there is no demonstrated effect on the plugin catalog or its validation. It should not be treated as a plugin filter or catalog setting. If you omit it, the execution method uses an internal default of None; no STRING default, length limits, or accepted options are specified. Any workflow-ordering behavior supplied by components outside this implementation is not established by the provided code.

OpenKatana · List plugins Output Parameters:

result_json

A STRING containing the formatted response from the OpenKatana tool invocation. The underlying plugin-listing function returns a result with three named components: plugins, which contains the catalog returned by the loaded plugin environment; browser, which records the browser version used for that session; and inputs, which contains the call’s provenance information for tracking execution inputs. These details help you inspect available extensions and retain context when comparing runs or diagnosing environment differences. The supplied code does not define the internal structure of each catalog entry, the exact provenance layout, or whether the response formatter places the result inside an additional wrapper, so inspect the returned JSON before configuring downstream field extraction. This output is text data, not an image, plugin installation, or rendered composition.

OpenKatana · List plugins Usage Tips:

  • Use the node to check plugin availability before running operations that depend on extensions. Inspect the returned catalog rather than assuming that a plugin is usable merely because its files exist on disk.
  • Keep project_id consistent with the project used by your related OpenKatana tools. Use the argument schema provided by your installed tool definition for arguments; the supplied implementation is not sufficient to give a reliable copy-and-paste argument example.
  • When preparing plugin manifests, use OpenKatana API version 1 and a plugin version written as three numeric components, such as 1.2.0. Each plugin needs a unique ID, and core is reserved.
  • Keep each plugin package focused and within the validation limits: the manifest collection is checked with a limit of 32 entries, and each plugin’s file list is checked with a limit of 128 entries. Each listed asset must be no larger than 8 MiB. These are package-validation constraints, not extra node settings.
  • Include the JavaScript entry file in the manifest’s file list, and include a license or notice file ending in .txt or .md. The manifest also requires a nonblank license provenance label.
  • Avoid editing, rebuilding, or replacing plugin files while the node is executing. Finish plugin updates before running the node so its input-integrity check sees a stable set of files.
  • Save the complete result_json when troubleshooting or documenting a workflow. The browser version and provenance information can help explain differences between runs, although this information alone does not guarantee identical behavior.
  • Leave after unconnected unless your wider workflow has a documented reason to use it. The shown execution method does not use it to change the listing request.

OpenKatana · List plugins Common Errors and Solutions:

Plugin requires OpenKatana API 1

  • Explanation: A plugin manifest does not declare API compatibility as the integer 1. A string such as "1" does not satisfy the explicit type check.
  • Solution: Use a plugin release compatible with OpenKatana API 1. If you maintain the plugin, verify its compatibility and set the manifest’s api field to the number 1 rather than a quoted string; changing the declaration alone does not make incompatible code compatible.

Duplicate or reserved plugin ID

  • Explanation: Two configured manifests use the same plugin ID, or a manifest uses the reserved ID core. OpenKatana requires distinct plugin identities.
  • Solution: Remove duplicate manifest references or use plugin packages with unique IDs. If you maintain a plugin, choose an ID other than core and update any references that depend on it.

plugin.version: expected X.Y.Z

  • Explanation: The manifest’s version is not a string containing exactly three dot-separated numeric components. Values such as 1.0, v1.0.0, or 1.0.0-beta do not match the shown validation rule.
  • Solution: Set the version to a string such as 1.0.0 or obtain a corrected manifest from the plugin provider.

plugin.license: required provenance label

  • Explanation: The manifest’s license field is missing, is not a string, or contains only whitespace. OpenKatana requires a nonblank label to record licensing provenance.
  • Solution: Add the plugin’s actual license or provenance label as a nonempty string. Use information supplied by the plugin author rather than guessing its license.

plugin.files must be unique and include entry

  • Explanation: The manifest’s file list contains a non-string item, repeats a filename, or does not include the declared entry file.
  • Solution: Make every file-list item a filename string, remove duplicate entries, and ensure that the value of entry appears exactly in the file list. Check folder names, spelling, and capitalization.

Include the plugin license/notice file

  • Explanation: The plugin’s listed files do not include a filename ending in .txt or .md, which the validator requires for a license or notice document.
  • Solution: Include the plugin’s actual license or notice document in the package and add its relative filename to the manifest’s file list. Keep the manifest’s license label populated as well; these are separate requirements.

Plugin file exceeds 8 MiB

  • Explanation: At least one file listed in the plugin manifest is larger than the permitted 8 MiB limit. Validation checks each listed file individually.
  • Solution: Identify the oversized asset and obtain or create a smaller supported version. If you maintain the plugin, reduce unnecessary packaged content and update the manifest and plugin references together so the package remains functional.

plugin.entry must be JavaScript

  • Explanation: The manifest’s entry filename does not end with .js. The provided check specifically requires that ending.
  • Solution: Point entry to the plugin’s actual JavaScript entry file, ensure its filename ends with lowercase .js, and include that same filename in the manifest’s file list. Renaming a non-JavaScript file is not a valid substitute.

Plugin inputs changed while executing

  • Explanation: A tracked plugin file’s digest changed during the execution session. This can occur when an editor, build process, synchronization tool, or another process modifies plugin resources while the node is running.
  • Solution: Stop processes that modify the plugin package, complete any updates, and run the node again with stable files. Avoid rebuilding plugins concurrently with inspection.

Plugin reference: plugin/name

  • Explanation: When OpenKatana validates a plugin reference, it expects a string with exactly two slash-separated parts in the form plugin/name. This is a related reference-validation error, not a guaranteed outcome of every catalog request.
  • Solution: If this error appears, check the relevant reference and use the plugin’s documented ID and item name with one separating slash. Both parts must also satisfy OpenKatana’s name validation.

unexpected inputs: ...

  • Explanation: The node received extra execution fields that are not among its supported typed inputs. The execution method explicitly rejects such fields before invoking the tool.
  • Solution: Use only the exposed inputs: project_id, arguments, and optional after. Do not add separate fields such as root paths or manifest lists to the node interface; supply any supported tool options through the documented argument mechanism.

Manifest, asset, or argument validation failure — exact message varies

  • Explanation: Other failures can occur while parsing manifest JSON, checking required fields, validating paths and permitted file types, enforcing collection limits, or preparing the tool arguments. The supplied excerpts do not show the exact error messages for these cases.
  • Solution: Read the returned error details and check the referenced resource. Confirm that manifests are valid JSON with the required api, id, version, entry, files, and license fields; verify that listed assets exist and use supported extensions: .js, .json, .txt, .md, .png, .jpg, .webp, or .svg. For argument-preparation failures, verify project_id and consult the installed tool’s argument schema rather than changing plugin files unnecessarily.

OpenKatana · List plugins Related Nodes

Go back to the extension to check out more related nodes.
OpenKatana
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.

OpenKatana · List plugins