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 > ComfyUI-MossPanelDataset > View and edit MOSS prompt

ComfyUI Node: View and edit MOSS prompt

Class Name

MossPromptEditor

Category
Manga panel dataset
Author
sepiablue-ai (Account age: 467days)
Extension
ComfyUI-MossPanelDataset
Latest Updated
2026-11-05
Github Stars
0.04K

How to Install ComfyUI-MossPanelDataset

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

View and edit MOSS prompt Description

Review MOSS prompts, preserve original text, or edit and validate JSON before workflow output.

View and edit MOSS prompt:

MossPromptEditor lets you review a generated MOSS prompt and choose whether to keep it unchanged or replace it with a manually edited JSON version. It is useful when you want to fine-tune a manga or panel-generation prompt without rebuilding the upstream settings that created it. Its two working paths support both straightforward pass-through and deliberate customization: unchanged text is preserved exactly, while edited text is checked for valid JSON and then serialized using the package’s JSON formatting routine. This helps catch formatting mistakes before an edited prompt continues through your workflow. The node checks JSON syntax, not whether the content follows every requirement of a downstream MOSS model, so you should preserve the expected prompt structure when making changes.

View and edit MOSS prompt Input Parameters:

プロンプト

This required STRING is the prompt received from an upstream node. It is configured as a connection-only input using forceInput=True, so you supply it through a connected text output rather than a normal text-entry widget. When the selected mode is “As received” (受け取ったまま), this text becomes the result without modification or JSON validation. In edited mode, it is not combined with your replacement text; instead, it remains the received text supplied to the node’s interface for review. Connecting a prompt-producing node such as MossPanelDatasetFlexible provides a practical starting point for editing an existing MOSS prompt. No default value or minimum or maximum text length is specified in this node.

使うプロンプト

This required COMBO[STRING] selects whether the node uses the received prompt or the edited version. The source explicitly identifies “As received” (受け取ったまま) as the pass-through choice: selecting it preserves the incoming text exactly and ignores the contents of the editing field. Any other recognized selection follows the edited-prompt path, which requires nonblank, valid JSON and reformats it through the package’s JSON serializer before returning it. The choices are supplied by options(EDITOR_MODES) and interpreted through the package’s localization helper, so labels can depend on the package’s language configuration. The provided source does not include the full option list or an explicit default, so the exact label of the edited-prompt choice cannot be confirmed here. Numeric minimum and maximum values do not apply.

編集用プロンプト

This required STRING is a multiline editing field with a default value of an empty string, "". Use it to enter the complete replacement JSON prompt, not just a sentence describing your desired change or a fragment to append to the original. It affects the result only when you select the edited-prompt path; in “As received” mode, it may remain empty without causing an error. When editing is enabled, an empty or whitespace-only value raises an error, and malformed JSON raises an error that identifies the line and column where parsing failed. Valid JSON is parsed and serialized again, so its spacing or formatting may change. No minimum or maximum text length is declared, although edited mode requires nonblank content. The node does not enforce a particular MOSS JSON structure, so syntactically valid text can still be unsuitable for your downstream workflow.

View and edit MOSS prompt Output Parameters:

MOSS prompt

This STRING is the selected prompt text to pass to the next stage of your workflow. In “As received” mode, it is exactly the incoming string, including its original formatting. In edited mode, it represents the JSON entered in the editing field after successful parsing and serialization with the package’s JSON formatting routine; it does not merge the edits with the received prompt. This distinction matters when checking your results: your replacement must contain everything the next stage needs. The output remains text rather than a separate JSON object, and successful execution confirms JSON syntax only for the edited path, not compatibility with a particular model or prompt schema. The node also sends the originally received text to its interface for display, but that interface data is not an additional output socket and does not necessarily represent the edited result.

View and edit MOSS prompt Usage Tips:

  • Start with 使うプロンプト set to “As received” and run the workflow once. The node’s own guidance recommends this step to populate the editing field with the received prompt, giving you an existing structure to modify rather than recreating it manually.
  • Use “As received” when you want an unchanged baseline or need to compare your edits against the original. This path does not parse or reformat the prompt, making it useful for confirming that the upstream prompt works before introducing changes.
  • Treat 編集用プロンプト as a complete replacement. Preserve the existing keys, lists, and structural relationships unless you know the downstream prompt format allows changes, and edit descriptive text or dialogue in place where appropriate.
  • Keep JSON punctuation intact: use double quotes around property names and text values, place commas between entries, and match every opening brace or bracket with a closing one. If dialogue contains quotation marks, escape them as \" inside a JSON string.
  • Make a small change, switch to the edited-prompt mode, and test it before making further changes. This makes it easier to identify whether an unexpected result comes from your wording, a structural change, or a JSON formatting mistake.
  • Check the outgoing MOSS prompt when verifying edits. The node explicitly supplies the original received text to its interface, so seeing the original there does not by itself prove that your edited prompt was ignored.

View and edit MOSS prompt Common Errors and Solutions:

"Edited prompt" is empty. Run once with "As received" to fill it with the received prompt.

  • Explanation: You selected the edited-prompt path, but 編集用プロンプト is empty or contains only whitespace. Although the field is listed as required, its default is empty; that default is acceptable only when the received prompt is being used.
  • Solution: Switch 使うプロンプト to “As received” and run once, following the node’s suggested initialization workflow. Check that the editing field contains the received prompt, make your changes, and then select the edited-prompt mode again. Alternatively, enter a complete, valid JSON prompt yourself.

"Edited prompt" is not valid JSON (line N, column M). Check brackets, commas, and quotes.

  • Explanation: The edited text could not be parsed as JSON. The actual message replaces N and M with the line and column where the parser detected the problem. Common causes include missing commas, trailing commas, mismatched braces or brackets, single quotes instead of double quotes, unescaped quotation marks inside dialogue, or plain text entered instead of JSON. The underlying mistake may occur just before the reported position.
  • Solution: Inspect the reported location and the preceding text. Restore missing punctuation, remove trailing commas, use double quotes for property names and string values, and escape quotation marks inside text as \". If you pasted from a formatted example, remove any Markdown code fences or explanatory text around the JSON. If the structure is difficult to repair, return to the received prompt and reapply your changes in small steps.

View and edit MOSS prompt Related Nodes

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

View and edit MOSS prompt