mirror of
https://github.com/langgenius/dify.git
synced 2026-10-04 13:47:55 +08:00
Charles YaoandClaude Opus 5
583f7fa55f
The App Builder composer's "Add missing details" link needs a backend. It fires in the pre-creation composer, so there is no app, no draft workflow and no Builder session yet -- it is tenant-scoped only, which puts it beside /workflow-generate/suggestions rather than under console/dify_builder. POST /console/api/workflow-generate/improve expands a short build instruction into one that states what a builder would otherwise have to ask about: the trigger and inputs, the steps, the rules that decide between outcomes, the output and its destination, and the failure path. Soft-fail like suggestions: no default model, an LLM error, an echo of the input, or a rewrite shorter than the input all return "" from the generator, and the route answers 200 with the caller's own text and changed=false. The action can never strand what the user typed, so there is deliberately no 402/429 mapping. Deliberately not grounded in the tenant's tools or knowledge bases. Naming tools here would prejudice the workflow generator's own tool router, which selects from the full installed catalogue against the instruction it is actually given -- and it keeps the endpoint free of DB and plugin-daemon calls. The boundary guard is split out rather than shared: _workflow_instruction_guard names ideal_output in its wording, which this payload does not carry. The existing endpoints' error strings stay byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>