代理開發平台
Dify 1.17 Packages Agent Environments as Restorable Snapshots While Overhauling the Runtime Backend and Environment Variables
Dify 1.17.0 adds the E2B runtime backend, build-time home snapshots, versioned Skills, and layered context compression, giving agents a consistent set of tools and file state on every startup. This is not a painless minor upgrade: database migrations, Compose configuration, and multiple environment variables have changed, so self-hosted users must revalidate their deployments.
The central change in Dify 1.17.0 is that the agent runtime environment is now part of the publishable artifact. When developers apply an agent build, the system captures packages, staged files, and working state from the sandbox home directory. When the published version is subsequently run, it restores that same snapshot. Compared with installing dependencies on demand for every run, this reduces environment drift and makes it possible to “validate at build time and replay at runtime.” In addition to the local sandbox, agent shells and code can now run through E2B by setting `DIFY_AGENT_RUNTIME_BACKEND`. The new Compose file includes the corresponding services, and E2B traffic requires authentication.
The workspace-level Skills manager adds draft, publish, and version lifecycles, packaging code, tool definitions, and operating rules as capabilities that agents can discover. For long conversations, Dify first removes old tool results and then summarizes earlier history, preserving recent messages within a budget based on the model’s actual context window. Version 1.17 also introduces vendor-neutral unified tracing that can create parent-child spans for workflows, loops, subprocesses, ReAct steps, and tool calls. Initial export integrations include Phoenix and LangSmith, but tracing is disabled by default.
Deployment risk cannot be assessed from the feature list alone. This release adds database migrations for Skills, the home snapshot ledger, and the new agent runtime. `EDITION` has been renamed to `DEPLOYMENT_EDITION`, while the previous agent timeout and shellctl variables have been replaced or removed. The default maximum runtime for applications and workflows has increased from 1,200 seconds to 3,600 seconds, potentially changing worker utilization and failure-recovery behavior. The official guidance also warns that creating the cleanup index on a large `conversations` table may take time, and teams using customized Compose configurations must manually reapply the changes. Engineering teams should first validate snapshot reproducibility, E2B network boundaries, compatibility with legacy Agent nodes, and migration duration in a staging copy before scheduling the production upgrade.