Implements the stage 1–5 program from #38174 (3.1 dropped per request). Backend (api/) - New POST /workflow-generate/suggestions: short, workspace-grounded example instructions generated on the tenant default model; soft-fails to {suggestions: []}. - New POST /workflow-generate/stream: SSE plan-first generation that emits the planner result (plan) then the built graph (result), reusing the existing planner/builder/validate stages — the streamed result provably equals the blocking /workflow-generate return. - mode:"auto" on both generate endpoints; a lightweight classifier resolves the concrete mode before planning and it is echoed back as `mode`. Frontend (web/) - Remove the low-value "Ideal output" field from the modal. - Replace the static example chips with AI-generated, workspace-grounded suggestions (cached per session per mode, ↻ refresh, silent static fallback). - Plan-first streaming: show the planner outline as it lands, then the graph (replaces the guessed phase timer) via an isolated SSE consumer that reuses the existing cookie-auth/CSRF/abort setup without touching handleStream. - Review stage: planner metadata header (icon + name), an actionable error panel (Regenerate / Install tools / affected node), a /refine diff summary, and a post-apply nudge toward cmd+k /refine. - Entry & input: ⌘/Ctrl+Enter to generate, autofocus, palette inline capture (`/create workflow <text>`), an "Auto" submenu option, and last-instruction resume across opens. i18n keys added across all 23 locales. New tests cover the suggestions component (fetch → fallback → refresh), the graph diff util, and the updated /create command. Refs #38174 Co-Authored-By: Claude Opus 4.8 (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 Claude.mdcd api 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