Component

core/ai-agent/dify-worker

The Dify task worker — the Celery consumer that runs everything a Dify installation does off the request path: indexing uploaded documents into the vector datastore, executing scheduled and queued workflow runs, generating dataset segments, and delivering mail and webhooks. It takes work from the Redis-compatible broker wired through the `cache` uses-socket, reads and writes the platform's relational model in the PostgreSQL backend wired through `backend`, and writes embeddings into the vector datastore wired through `vector_store`. Workflow code nodes it executes run in the sandbox wired through `sandbox`, and outbound requests to addresses a user supplied are routed through the forward proxy wired through `ssrf_proxy`. It serves no port and nothing connects to it — work reaches it through the broker — so it publishes no provides contract and renders as a stateless worker tier. By default nothing reaches Dify's vendor: infra.telemetry_enabled turns on its daily usage event, and infra.marketplace_enabled its daily plugin upgrade check against the plugin marketplace.

Version

1.0.01.1.0

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:3fe0f7701ed392f6517da04e6d5c7168044cc4ca129ec2430b8abbe34d6969e9
Published
2026-11-15T08:08:52Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:9993f64b63ebc9759ad16bdd7e5e06f5750ca9654bc22e50473426a23a092ea8

Reference at this version

oci://hub.aggrega.ai/component/core/ai-agent/dify-worker:1.1.0

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
vector_index_prefixstringVector_indexnoName prefix the worker gives the collections it creates in the wired vector datastore. It matches the API server's prefix, because the two write the same collections.
indexing_max_segmentation_tokensinteger (min 1)4000noLongest segment, in tokens, the dataset indexer produces when it splits a document.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
engine_versionstring1.17.0noDify API container image tag. The API server, the scheduler and this worker run the same image, so a Release moves all three together.
log_levelstring (DEBUG | INFO | WARNING | ERROR | CRITICAL)INFOnoLog verbosity the worker emits.
concurrencyinteger (min 1)4noNumber of task slots one worker process runs in parallel. Raising it raises throughput and the worker's memory ceiling together, so it is sized with compute.memory.
telemetry_enabledbooleanfalsenoLets the worker send Dify's anonymous daily usage event, and the install event when the server's own was not delivered, to otel.dify.ai, falling back to otel.dify.cn. Unset or false, nothing reaches those hosts. Set it on the server and the scheduler too.
marketplace_enabledbooleanfalsenoLets the worker reach Dify's plugin marketplace (marketplace.dify.ai): the daily plugin upgrade check the scheduler enqueues, and installing the plugins a new workspace is configured with. Model-provider plugins such as OpenAI's install from the marketplace, so a Release whose applications use one sets it. Unset or false, nothing reaches that host. Set it on the server and the scheduler too.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

No output values declared.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

backend

Selector
component.aggrega.ai/category=datastore
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional password the worker presents to the backend this connection reaches, shared with that backend. When attached, supplies the backend password via the credential subsystem; unattached, the Recipe uses the development literal `apppass`, which this catalog publishes, so every Release that leaves the slot unattached shares that password.

cache

Selector
component.aggrega.ai/category=datastore
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
server_cafeature.aggrega.ai/kind=secretnofileyesOptional authority the worker checks the cache's certificate against while the cache publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and points the cache client and the task broker at the file. The build halts on a server_ca publishing no Secret name, and on one wired to a cache served without TLS. Fill it with core/referenced-secret.

vector_store

Selector
datastore.aggrega.ai/engine in (vector, semantic-memory, search)
Inject
env

This socket declares no attachment slots, so a connection through it carries no attachment.

sandbox

Selector
component.aggrega.ai/category=ai-agent
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional execution-key credential the worker presents on every request to the sandbox this connection reaches. The same credential is attached to the code_execution_key slot on the sandbox, so both ends hold the same value. Unattached, the Recipe uses the pinned development literal `dify-sandbox`, suitable for evaluation only and published in this catalog, so every Release that leaves the slot unattached shares it.

plugin_daemon

Selector
component.aggrega.ai/category=ai-agent
Inject
env

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional credential the worker presents on every call it makes to the plugin runtime this connection reaches. The runtime holds the same key in its plugin_daemon_key slot and the API server presents it on its own connection, so the credential is attached to all three or to none: attaching it to some of them leaves the rest carrying a different value, which renders cleanly and is refused when the call is made. Unattached, the Recipe uses the pinned development literal `dify-plugin-daemon-server-key`, suitable for evaluation only and published in this catalog, so every Release that leaves the slot unattached shares it.

ssrf_proxy

Selector
component.aggrega.ai/category=ai-agent
Inject
env

This socket declares no attachment slots, so a connection through it carries no attachment.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

SlotSelectorRequiredInjectSensitiveDescription
secret_keyfeature.aggrega.ai/kind=secretyesenvyesRequired application-secret credential. The worker decrypts stored model-provider credentials under it, so it carries the same secret as the API server. There is no default: the build halts when nothing fills this slot.
inner_api_keyfeature.aggrega.ai/kind=secretnoenvyesOptional credential the plugin runtime presents on every call back into the internal API, which the worker compares against its own. The worker and the API server declare this slot under the same name and the plugin runtime presents it on its connection to the API server, so the credential is attached to all three or to none: attaching it to some of them leaves the rest carrying a different value, which renders cleanly and is refused when the call is made. Unattached, the Recipe uses the pinned development literal `dify-plugin-inner-api-key`, suitable for evaluation only and published in this catalog, so every Release that leaves the slot unattached shares it.

Self-inject allowlist

env

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy