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

Component

core/ai-agent/librechat

A self-hosted LibreChat installation — the browser platform a person holds conversations in, and the tier that turns a bare model endpoint into a working assistant surface. It reaches its model through the `model` uses-socket and adds agents an author assembles without writing code, tool invocation over the tool servers an administrator registers, a code interpreter, and retrieval over files a user uploads. Every agent run, a delegated child run included, is entered from a conversation a person started: the platform runs no background loop of its own. Its accounts, conversations, agents and stored per-user credentials live in a document store wired through the `backend` socket, the system of record; only uploaded files sit on a volume of its own. The two token-signing secrets and the credential-encryption pair decide what its sign-ins and stored credentials are worth, and each has a slot of its own. None of the four has a default, and the build halts until each slot is filled. On Kubernetes, reach for `librechat-chart`, rendering the project's own chart, where a chart repository is reachable at build time, and for `librechat`, the workload synthesis, where the build must fetch nothing. With `values.metrics_enabled` true each Recipe turns on the platform's Prometheus metrics, at /metrics on its port and answered only to a bearer token equal to the secret attached to metrics_secret, and publishes the address as `metrics_endpoint`; a scrape presents that secret on its connection's `credential` slot.

Versión

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:a5c1bbdc5144e1318fbc340c96100e55df2023fbe94e4d9af60bce81e6d66385
Publicado
2026-11-10T10:08:20Z
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:5e2d83ae435662218bf88ae3dd556a220e64318c20994c31847e0381788d2df7

Referencia en esta versión

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

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

Extiende BaseComponents#/schemas/BaseAgentParameter

NombreTipoPredeterminadoObligatorioDescripción
app_titlestringLibreChatnoName the platform presents in the browser title and the interface header. Two installations reachable by the same people tell themselves apart by carrying different titles.
database_namestringLibreChatnoName of the logical database the platform uses inside the wired document store. Two installations sharing one store keep their data apart by carrying different names.
allow_registrationbooleanfalsenoWhether a visitor who is not yet a user may create an account from the sign-in page. Left off, accounts are created only by an administrator, which is the posture an installation reachable beyond its own team wants.
metrics_enabledbooleanfalsenoTurns on LibreChat's own metrics, in the Prometheus format, at /metrics on the platform's port, and publishes their address as `metrics_endpoint`; while false that key is empty. The platform answers them only to the secret attached to metrics_secret, presented as a bearer token, so the build halts when this is true and that slot is unfilled. They carry request counts and timings, never a user's or conversation's identifier or content.

Dimensionamiento del operador

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

NombreTipoPredeterminadoObligatorioDescripción
portinteger (min 1024, max 65535)3080noListen port the platform serves its interface and API on, and the port consumers connect to. Most operators should omit this and let the Recipe assign the default (3080).
engine_versionstringv0.8.7noLibreChat container image tag. Selects the image tag of the platform container on both Recipes.
source_versionstring—noVersion of the platform's own Helm chart the chart-backed Recipe pulls, defaulting to the version that Recipe was checked against. The workload-synthesis Recipe pulls no chart and reads nothing here.
storageobject—no—
external_base_urlstringnoExternally reachable base URL of the installation, as a browser sees it — the address the ingress tier publishes. The platform composes the links it emits from it and accepts browser requests against it. Left empty, the Recipe supplies the installation's own in-cluster address instead, which suits an installation reached only in-cluster.
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
hoststring—síIn-cluster DNS name of the Service serving the chat interface and its API. The ingress tier points its upstream at this name.
portinteger—síTCP port that Service serves the interface and API on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
protocolstring—noURL scheme to reach `host` and `port` over, which a consumer composes its base URL on.
metrics_endpointstring—noThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<port>/metrics`, on the port the interface is served on. Empty while values.metrics_enabled is false.
metrics_credential_requiredboolean—noWhether a scrape of `metrics_endpoint` must present a credential: true while values.metrics_enabled is true, because the platform answers its metrics only to the secret attached to metrics_secret, which a scrape presents on its connection's `credential` slot; false while no address is published.

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.

model

Selector
component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
Inyección
—

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

SlotSelectorObligatorioInyecciónSensibleDescripción
credentialfeature.aggrega.ai/kind=secretnoenvsíOptional credential the platform presents to the model this connection reaches. Unattached, the Recipe leaves the platform in its per-user mode, where each person enters their own key in the interface and no key is rendered at all.

backend

Selector
component.aggrega.ai/category=datastore
Inyección
—

Este socket no declara slots de acoplamiento, por lo que una conexión a través de él no lleva ningún acoplamiento.

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.

SlotSelectorObligatorioInyecciónSensibleDescripción
session_secretfeature.aggrega.ai/kind=secretsíenvsíRequired secret the platform signs its access tokens with. There is no default: the build halts when nothing fills this slot. Blanking the variable instead, so the platform generates one for itself, is a bootstrap convenience rather than a credential-rotation system: the generated value does not survive a restart and a second replica generates a different one, and each change invalidates every session then active.
session_refresh_secretfeature.aggrega.ai/kind=secretsíenvsíRequired secret the platform signs its refresh tokens with — the tokens a browser presents to mint a new access token, so it carries the weight of the access-token secret. There is no default: the build halts when nothing fills this slot. Blanking the variable instead, so the platform generates one for itself, is a bootstrap convenience rather than a credential-rotation system: the generated value does not survive a restart and a second replica generates a different one, and each change makes every person sign in again.
credential_encryption_keyfeature.aggrega.ai/kind=secretsíenvsíRequired key the platform encrypts the credentials it stores in the document store under, as 64 hexadecimal characters (a 32-byte key). It encrypts the credentials it supports whether or not the people using the installation ever save one of their own, so this slot is filled even where the model key is supplied centrally. There is no default: the build halts when nothing fills this slot. Blanking the variable instead, so the platform generates one for itself, is a bootstrap convenience rather than a credential-rotation system: the generated value does not survive a restart and a second replica generates a different one, and each change leaves everything already stored undecryptable.
credential_encryption_ivfeature.aggrega.ai/kind=secretsíenvsíRequired initialization vector the platform pairs with the credential-encryption key when it encrypts what it stores, as 32 hexadecimal characters (16 bytes). A vector is not secret by cryptographic design, but one every reader of this catalog held would be the same in every Release, so there is no default: the build halts when nothing fills this slot. Blanking the variable instead, so the platform generates one for itself, is a bootstrap convenience rather than a credential-rotation system: the generated value does not survive a restart and a second replica generates a different one, and each change leaves everything already stored undecryptable.
metrics_secretfeature.aggrega.ai/kind=secretnoenvsíOptional secret the platform answers its Prometheus metrics to: a scrape presents it as a bearer token, on its connection's credential slot. It is delivered as METRICS_SECRET only while values.metrics_enabled is true, and is required then: the build halts when the value is true and nothing fills this slot. There is no default. While the value is false it is not delivered, and the platform answers its metrics route 401 to every caller.

Lista de permitidos de autoinyección

No se declararon canales de autoinyección.

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