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>
Dify Backend API
Setup and Run
Important
In the v1.3.0 release,
poetryhas been replaced withuvas the package manager for Dify API backend service.
uv and pnpm are required to run the setup and development commands below.
Using scripts (recommended)
The scripts resolve paths relative to their location, so you can run them from anywhere.
-
Run setup (copies env files and installs dependencies).
./dev/setup -
Review
api/.env,web/.env.local, anddocker/middleware.envvalues (see theSECRET_KEYnote below). -
Start middleware (PostgreSQL/Redis/Weaviate).
./dev/start-docker-compose -
Start backend (runs migrations first).
./dev/start-api -
Start Dify web service.
./dev/start-web./dev/setupand./dev/start-webinstall JavaScript dependencies through the repository root workspace, so you do not need a separatecd web && pnpm installstep. -
Set up your application by visiting
http://localhost:3000. -
Start the worker service (async and scheduler tasks, runs from
api)../dev/start-worker -
Optional: start Celery Beat (scheduled tasks).
./dev/start-beat
Environment notes
Important
When the frontend and backend run on different subdomains, set COOKIE_DOMAIN to the site’s top-level domain (e.g.,
example.com). The frontend and backend must be under the same top-level domain in order to share authentication cookies.
-
Generate a
SECRET_KEYin the.envfile.bash for Linux
sed -i "/^SECRET_KEY=/c\\SECRET_KEY=$(openssl rand -base64 42)" .envbash for Mac
secret_key=$(openssl rand -base64 42) sed -i '' "/^SECRET_KEY=/c\\ SECRET_KEY=${secret_key}" .env
Testing
-
Install dependencies for both the backend and the test environment
cd api uv sync --group dev -
Run the tests locally with mocked system environment variables in
tool.pytest_envsection inpyproject.toml, more can check AGENTS.mdContinue in the
apidirectory from the previous step.uv run pytest # Run all tests uv run pytest tests/unit_tests/ # Unit tests only uv run pytest tests/integration_tests/ # Integration tests # Code quality ../dev/reformat # Run all formatters and linters uv run ruff check --fix ./ # Fix linting issues uv run ruff format ./ # Format code uv run pyrefly check # Type checking
Generate TS stub
uv run dev/generate_swagger_specs.py --output-dir openapi
use https://jsontotable.org/openapi-to-typescript to convert to typescript