OpenKatana · Open Studio:
OpenKatanaWorkspace creates or reopens a local OpenKatana project and its Studio, giving you a starting point for working on a creative project from ComfyUI. It serves as a workspace setup node rather than an image or video generation node: its purpose is to establish access to your project and the Studio associated with it. The node also supports OpenKatana’s workflow of copying CLI/MCP setup information to your agent, allowing you to connect an assistant through command-line tools or the Model Context Protocol. This helps you work with a project across ComfyUI, Studio, and agent-based tools without treating each application as a separate project environment. The operation uses OpenKatana’s local Studio functionality and does not itself perform paid or cloud-based generation.
OpenKatana · Open Studio Input Parameters:
project_id
A required STRING that identifies the local project you want to create or reopen. The default value is my-film. This value is passed to OpenKatana’s Studio operation to select the project, so keeping it consistent is important when you want to return to the same workspace. For example, you could use forest-short to distinguish a short-film project from another project. No minimum or maximum length, allowed-character rules, or predefined options are specified in the supplied node code; do not assume that every possible string is accepted by the underlying project system. A short, recognizable identifier is a practical choice, but no particular naming format is enforced by this node itself.
name
A required STRING supplying the project name to the Studio operation. The default value is My film. This lets you provide a readable title, such as Forest Short Film, alongside the project identifier. Both values are passed to OpenKatana when creating or reopening the workspace, but the supplied code does not show whether changing this name renames an existing project or only affects project creation. No minimum or maximum length, predefined options, or other validation rules are specified. When reopening an existing project, keep its established name unless you have confirmed how OpenKatana handles name changes.
OpenKatana · Open Studio Output Parameters:
result_json
A STRING containing the response produced by the OpenKatana Studio operation and processed by the bridge’s response helper. This is the node’s textual result, not an image, video, or model output. You can inspect it to understand what the workspace operation returned and use any setup information it provides when connecting your agent. Although the output is named result_json, the supplied context does not define the response schema or show the response helper’s implementation, so specific fields, status values, URLs, paths, or setup commands cannot be guaranteed. Treat the returned content as the authoritative result for that execution rather than assuming a fixed set of fields.
OpenKatana · Open Studio Usage Tips:
- Choose a distinct
project_idfor each separate creative project, and reuse that exact value when reopening it. For example, pairforest-shortwith the readable nameForest Short Film. - Replace the defaults when starting separate projects. Leaving
project_idasmy-filmacross multiple workflows may direct them to the same project rather than giving each workflow its own workspace. - Use this node for workspace setup, not generation. There are no model, resolution, quality, or speed settings in its interface, so generation-performance tuning belongs elsewhere in your workflow.
- Inspect
result_jsonafter execution. Follow the CLI/MCP setup information provided through the workspace operation or Studio rather than guessing commands or connection details. - Expect the workspace operation to run again when the node executes. It inherits an always-changed setting because OpenKatana project state can also change through Studio, CLI, or MCP; an unchanged pair of inputs does not mean ComfyUI will reuse an earlier result.
- When reopening an existing workspace, keep both values consistent initially. This reduces ambiguity while checking that you have returned to the intended project, especially because existing-project name-update behavior is not shown in the supplied code.
OpenKatana · Open Studio Common Errors and Solutions:
Missing required input: project_id or name
- Explanation: Both inputs are required by the node interface. If either is absent from a submitted workflow, ComfyUI may reject execution before OpenKatana is called. The exact validation message is not supplied in the source.
- Solution: Make sure both inputs are present. Start with
my-filmandMy filmif you are testing the node, then replace them with your intended project identifier and title.
Project creation or reopening fails
- Explanation: The node delegates workspace creation and reopening to OpenKatana. The supplied code does not include that operation’s validation rules or error messages, so the cause must be determined from the returned response or execution log.
- Solution: Read
result_jsonand the ComfyUI console for the specific failure. Check the project identifier first, and address any reported setup, storage, or access problem before rerunning the node.
The wrong project is reopened
- Explanation: This is a workspace-selection symptom, not a confirmed error message. Reusing another project’s
project_id, including the defaultmy-film, can select a project other than the one you intended. - Solution: Verify
project_idagainst the project you want to use. Choose a distinct identifier for a separate project rather than changing onlyname.
Studio is not accessible after execution
- Explanation: This is a troubleshooting symptom rather than a source-defined error. The node invokes the Studio operation, but the supplied implementation does not establish browser-opening behavior or guarantee a particular access address.
- Solution: Check the returned response and ComfyUI console for access instructions or a reported failure. If an address is provided, open that address manually. Follow any reported local setup requirements rather than assuming the browser must open automatically.
Expected fields are missing from result_json
- Explanation: The response structure is not documented in the supplied code. Assuming that the output always contains a particular URL, command, or status field can make a successful response appear incomplete.
- Solution: Inspect the complete returned string before building downstream parsing around it. Use only fields confirmed in your actual response, and consult the Studio’s available setup information when configuring CLI/MCP access.
