Эта страница переведена автоматически. Читать английский оригинал.

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. A store that requires a sign-in, as FerretDB does by default, takes the user and password from the credential attached on that connection. 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.

Версия

Происхождение

ОфициальныйПодписано идентичностью подписи, которую этот каталог признаёт официальным издателем.
Дайджест содержимого
sha256:592d4a83b2f5fe0574aaf9a1b2b37e6ad350ef54112d34906bd5444e7224c385
Опубликовано
2026-11-12T20:47:23Z
Идентичность подписи
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/dev

Подпись

  • Официальныйapplication/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/dev

    sha256:fbd85cd707a558aca4a1dc988647ccda749aea924c175cceda57be4559aa7c45

Ссылка на эту версию

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

Параметры разработчика

Значения, которые разработчик задаёт в сущности Aggregate.

Расширяет BaseComponents#/schemas/BaseAgentParameter

ИмяТипПо умолчаниюОбязательныйОписание
app_titlestringLibreChatнетName 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_namestringLibreChatнетName 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_registrationbooleanfalseнетWhether 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_enabledbooleanfalseнетTurns 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.

Размеры, задаваемые оператором

Размеры инфраструктуры, которые оператор настраивает для каждого окружения.

ИмяТипПо умолчаниюОбязательныйОписание
portinteger (min 1024, max 65535)3080нетListen 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.7нетLibreChat container image tag. Selects the image tag of the platform container on both Recipes.
source_versionstring—нетVersion 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—нет—
external_base_urlstringнетExternally 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—нет—
overridesobject (open)—нетProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Контракт выходных значений

Значения, которые этот компонент публикует для потребителей через топологию uses.

ИмяТипПо умолчаниюОбязательныйОписание
hoststring—даIn-cluster DNS name of the Service serving the chat interface and its API. The ingress tier points its upstream at this name.
portinteger—да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—нетURL scheme to reach `host` and `port` over, which a consumer composes its base URL on.
metrics_endpointstring—нетThe 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—нетWhether 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.

Сокеты uses

Сокеты зависимостей, через которые подключается этот компонент. Цель каждого соединения, проведённого через сокет, должна удовлетворять его селектору меток, и каждое соединение может нести подключение в слотах, которые объявляет сокет. Обязательный слот должен заполнить каждое соединение, которое сущность Aggregate или сущность Release проводит через сокет.

model

Селектор
component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
Внедрение
—

Слоты, которые может заполнить каждое соединение через этот сокет

СлотСелекторОбязательныйВнедрениеКонфиденциальныйОписание
credentialfeature.aggrega.ai/kind=secretнетenvда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

Селектор
component.aggrega.ai/category=datastore
Внедрение
—

Слоты, которые может заполнить каждое соединение через этот сокет

СлотСелекторОбязательныйВнедрениеКонфиденциальныйОписание
credentialfeature.aggrega.ai/kind=secretнетenvдаOptional sign-in the platform presents to the document store this connection reaches, written as <user>:<password> with any reserved URL character in either part percent-encoded, since it becomes the user-information part of the connection string. Unattached, the connection string carries no user part.

Слоты подключения

Именованные точки привязки, в которых Feature подключается к этому компоненту. Селектор слота ограничивает, какая сущность Feature может его заполнить, а его список внедрения указывает, как могут доставляться материалы сущности Feature. Обязательный слот должен быть привязан в каждом экземпляре — подключением в самом экземпляре или в области выше него, — а конфиденциальный слот объявляется для работы с секретными материалами. Feature также может подключаться под именем, которое не объявляет ни один слот.

СлотСелекторОбязательныйВнедрениеКонфиденциальныйОписание
session_secretfeature.aggrega.ai/kind=secretдаenvда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=secretдаenvда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=secretдаenvда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=secretдаenvда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=secretнетenvда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.

Список разрешённых самовнедрений

Каналы самовнедрения не объявлены.

Связи

Типизированные рёбра к другим опубликованным сущностям и от них. Ссылка без опубликованной цели отображается как разорванное ребро, а не как ссылка.

Использует

Используется в

Справочник по понятию Component →

Каталог Aggrega — открытый указатель компонентов, функций, рецептов и плагинов, которые их рендерят.

Создано на общей дизайн-системе Aggrega.

Конфиденциальность