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.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:648713c0f2d09a679fa04c037752a2a9f7fa500508eea246e7ebfb4fda644066
Published
2026-11-10T10:08:23Z
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:ffeddc53edfaf2158dbf9960cf1f25eeaaa0b3a74f99d29b1aceefefe716cbad

Reference at this version

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

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
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.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
imagestring—yesContainer 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.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
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.

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.

media_server

Selector
component.aggrega.ai/category=messaging, component.aggrega.ai/type=server
Inject
env, file

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretyesenvyesSigning 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.

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.

No attachment slots declared.

Self-inject allowlist

env, file

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