Esta página se tradujo automáticamente. Leer el original en inglés.

Component

core/ai-agent/livekit-agent-worker

A LiveKit agent worker — the resident process that joins a realtime room as a participant and runs the agent's own code there: the speech pipeline, or the realtime model, that holds the conversation with whoever else is in the room. It registers with the media server and runs one agent session for each job it is handed; it serves no application traffic, so no other component addresses it. Wire here when the conversation inside the cluster's own rooms is to be carried by software it runs and by agent code written for it, rather than handed to a hosted agent platform. Upstream publishes the agent framework as a language package rather than as a container image, and this component pins no image because there is none to pin. The image is a required operational value carrying no default, so using this component means building an image from the framework together with the agent code, publishing it where the cluster can pull it, and naming that reference in the Release. Nothing renders until that reference is supplied. Consumers receive the dispatch name the worker registers under; the worker publishes no host and no port. Realized by a Helm Recipe that synthesizes a Deployment over the supplied image and declares no Service and no volume for state. The connection to the media server needs no `inject:` block; one it writes delivers further names, as variables or files. The worker serves Prometheus metrics only where the agent's own code gives it a metrics port, which no environment variable or setting here reaches, so it publishes no metrics address, and a worker is not a target the catalog's Prometheus scrapes. The component's own `inject:` block takes `env` and `file` entries.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:648713c0f2d09a679fa04c037752a2a9f7fa500508eea246e7ebfb4fda644066
Publicado
2026-11-10T10:08:23Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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:ffeddc53edfaf2158dbf9960cf1f25eeaaa0b3a74f99d29b1aceefefe716cbad

Referencia en esta versión

oci://hub.aggrega.ai/component/core/ai-agent/livekit-agent-worker:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
agent_namestring—noDispatch name the worker registers under. Naming it turns on explicit dispatch — the server then hands this worker only the rooms a dispatch rule or an access token names it in, so several agents can serve different rooms of one media server. Leaving it unset keeps automatic dispatch, where the worker is offered every room the server opens, which is the shape a Release running a single agent wants. The name reaches the worker as a default the framework reads on startup, so an agent whose own code names itself keeps the name its code sets and this field has no effect on it.

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
imagestring—síContainer image reference the worker runs, including its tag or digest. It carries no default and the catalog pins nothing, because the agent framework is published as a language package rather than as a container image — an image for this component is built from that framework together with the agent code written for it, published where the cluster can pull it, and named here. A build that omits it halts.
log_levelstring (debug | info | warn | error)infonoWorker log verbosity.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

NombreTipoPredeterminadoObligatorioDescripción
agent_namestring—noDispatch name the worker registered under, carried through from the value the Aggregate declared. A consumer names it when it asks for an agent to be sent into a room, which is how the request reaches this worker rather than another.

Sockets uses

Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.

media_server

Selector
component.aggrega.ai/category=messaging, component.aggrega.ai/type=server
Inyección
env, file

Slots que cada conexión a través de este socket puede llenar

SlotSelectorObligatorioInyecciónSensibleDescripción
credentialfeature.aggrega.ai/kind=secretsíenvsíSigning secret paired with the api_key identifier this connection carries. Attach the same credential the media server holds: the worker authenticates to that server with this pair, so two different secrets leave the worker unable to register.

Slots de acoplamiento

Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.

No se declararon slots de acoplamiento.

Lista de permitidos de autoinyección

env, file

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

Usado por

Referencia del concepto Component →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad