Skip to content

Dify 1.20.0 adds OpenTelemetry traces and file scanning

Dify's 1.20.0 release adds OpenTelemetry trace export, malware scanning for knowledge uploads, human-in-the-loop approvals and personal access tokens for its OpenAPI.

Draftship Editorial3 min read

Dify 1.20.0, released on 18 November, adds OpenTelemetry trace export, malware scanning for knowledge uploads and personal access tokens for its OpenAPI. The release also brings human-in-the-loop approvals into email and team messaging tools, and lets Chatflow users watch Agent tool calls as they happen. The Dify 1.20.0 release notes list the new features, configuration changes, database migrations and upgrade steps.

Traces, approvals and file checks

A new OpenTelemetry provider lets Dify send app and Agent traces to any compatible collector. That lets teams follow workflow steps, model calls and tool activity in their existing observability stack. Tracing to Langfuse now works with v4 and the current Langfuse Cloud ingestion service. Existing Langfuse configurations continue to work, according to the notes. This matters because Langfuse Cloud retired its legacy ingestion endpoint on November 16, 2026, and self-hosted Langfuse v4 rejects events sent to it. The notes say users must upgrade to 1.20.0 to keep delivering traces to those deployments.

New HITL adds shared channels, centralized contacts, notification templates and verified approval forms. Teams can configure email and an IM platform, including Slack, Feishu/Lark, Microsoft Teams, DingTalk or WeCom, then reuse recipients across Human Input nodes. Approvers can act in supported IM cards or standalone forms, with Dify login or email verification. The feature is enabled by default with NEXT_PUBLIC_ENABLE_HITL_IM=true, and existing workflows can move legacy Human Input nodes with an opt-in migration.

Uploaded knowledge files can be checked for malware before Dify extracts or indexes them. When FILE_SCAN_ENABLED=true, workspace owners and admins configure scanners under Integrations → File Security Scan. Supported scanners are Cloudmersive, Scanii, OPSWAT MetaDefender Cloud and a Custom Endpoint. Each knowledge base can choose a scanner and fallback behavior. Scanning covers classic knowledge bases, RAG Pipeline local-file sources and Agent Knowledge Base uploads, and blocked files appear in the document list with a reason.

More control for scripts and Chatflows

With personal access tokens, scripts, CI jobs and personal agents can call the Dify OpenAPI as a user, without a shared Console session. Users create a token from the Account page and scope it to specific workspaces and resources. Tokens can have an expiration date, have their scope updated, or be revoked. The release also changes OPENAPI_ENABLED to true by default, so /openapi/v1/* endpoints are enabled out of the box for personal access tokens and difyctl. Operators can set it to false to disable the endpoints.

When a Chatflow hands work to an Agent v2 node, users can now see the tools it calls as they run. The tool calls sit beside the response in previews and published chats, and each card expands to show the request and result. This requires NEXT_PUBLIC_ENABLE_AGENT_V2_IN_CHATFLOW=true. A new GitHub picker presents repositories, directories, issues and pull requests in an expandable tree, so users can import chosen pages. The notes mention performance work, clearer document failure messages, layout and authentication page fixes, and security fixes.

Limits and open questions

The source does not put a number on the performance gains or say how much latency file scanning adds. It does not state whether every feature is available on Dify Cloud or whether the scanner vendors charge for use. It also does not say whether the new HITL approval UI changes existing workflows without the opt-in migration. This suggests teams relying on Langfuse need to upgrade before sending traces to Langfuse Cloud or self-hosted v4, though the source gives no deadline beyond the November 16, 2026 retirement.

What this means for building AI apps

For builders running Dify, the release pushes observability and approval steps into the same tools teams already use. The OpenAPI default is worth checking before an upgrade because it exposes endpoints unless an operator turns them off. File scanning depends on FILE_SCAN_ENABLED=true, but the source does not say the default.

If you are considering a hosted app builder alongside Dify, Draftship is an AI app builder where you describe an app in plain language and it writes the code, builds it and hosts it. Apps get a built-in database, user sign-in and hosting, and paid plans add private projects, a choice of AI model, source code access, custom domains and GitHub push. Its guide to adding AI to your app covers that route. Draftship is not affiliated with Dify.

Primary sources

  • v1.20.0 · Dify releases, Nov 18, 2026

This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.