You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] generation: No actionable setup entry when no model is configured #370
When no model is available for the selected generation type, the workspace shows a disabled "No generation model configured" control. It explains why generation is unavailable but provides no actionable path to configure a model, interrupting the creation flow.
This was reported from the video-generation panel. In src/canvas/NodeComposer.tsx, the model selector is disabled when serviceModels.length === 0.
Steps to reproduce
Open a workspace without an available video-generation model.
Create or select a video node and open its generation panel.
Inspect the model selector at the bottom of the panel.
Actual behavior
The selector displays an unconfigured-model placeholder and is disabled. The user must independently find Settings and the model connection page.
Expected behavior
The empty state provides an actionable "Configure video model" button that opens Settings → Model connections at the corresponding category and setup entry. Image and audio panels should handle the same condition consistently. A configured model in another category should not hide this action.
Returning from setup must preserve the prompt, references, parameters and selected node. Saving a model should refresh the available choices; cancelling or failing setup must not discard the draft. Configuration must not automatically submit generation or trigger a paid call.
Acceptance criteria
A click or keyboard activation opens the correct model configuration category from the empty state.
Saving, cancelling or failing setup preserves the existing creation context; newly saved compatible models become selectable.
Existing model selection, running-task restrictions and generation validation remain effective.
English and Chinese UI text and focus restoration are verified; npm run check:i18n passes.
Evidence and scope
Based on the reported workspace screenshot and inspection of the disabled-selector condition. No real-provider call is required to reproduce the empty state. This issue reports an existing usability gap; it does not assign implementation work to the reporter.
changed the title [-][feat] generation: 未配置模型时提供直接配置入口[/-][+][bug] generation: No actionable setup entry when no model is configured[/+]on Nov 16, 2026
Hi, I would like to take this one. My plan: Settings already opens on the Model connections page, so I will let the composer ask for a specific model category (image, video or audio) and show a "Configure ... model" button in the empty state of the model selector. The dialog opens directly on that category, the composer stays mounted underneath so the prompt, references and parameters are kept, and nothing is submitted. I will add both English and Chinese strings and run npm run check:i18n. Let me know if you would rather have a different approach.
Activity
[-][feat] generation: 未配置模型时提供直接配置入口[/-][+][bug] generation: No actionable setup entry when no model is configured[/+]Maurokrekels commentedon Nov 18, 2026
Hi, I would like to take this one. My plan: Settings already opens on the Model connections page, so I will let the composer ask for a specific model category (image, video or audio) and show a "Configure ... model" button in the empty state of the model selector. The dialog opens directly on that category, the composer stays mounted underneath so the prompt, references and parameters are kept, and nothing is submitted. I will add both English and Chinese strings and run
npm run check:i18n. Let me know if you would rather have a different approach.[feat] canvas: open model settings from an empty model selector