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

Component

core/ai-agent/agenta-web

The browser console of an agent workspace — the front end a team builds its agents on. It is where an agent is described in chat, its tools and skills are connected, its permissions are set, its version history is compared, and the trace of a finished run is read. It is a server-rendered front end and holds no state. Each page it renders is assembled from the control-plane API wired through the `api` socket and the model-facing service wired through `services`, and the two are separate sockets because they are separate services with separate addresses: agent definitions and traces come from the first, a playground completion from the second. Sign-in runs against the authentication core wired through `auth_core`, which the front end addresses by that core's own base URL. Wire here for the human surface. It carries no data of its own, so it is the one tier of the platform that can be scaled or restarted without consequence, and an Aggregate that only needs the API — automation driving the platform from outside — can leave it out. Exports its host, port, endpoint and protocol to consumers via the uses topology, which is what the ingress tier routes the browser path to. Realized on Kubernetes via its Helm Recipe, which synthesizes the front end as a stateless Deployment behind a ClusterIP Service on its HTTP port. Two kinds of address are emitted separately and deliberately: the in-cluster Service names it calls while rendering a page, and the external base URL the browser itself calls, which the operator supplies because a Service name does not resolve outside the cluster.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:17af94a055b8d65143e7fee39c6fd1175ab797755eff9c1f3490361acacfda2c
Publicado
2026-11-10T10:07:28Z
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:909b18db4cb215f839167d32e492fc4f7bc55d4b2539f116ba04b03b5a0a38ea

Referencia en esta versión

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

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
mobile_redirect_enabledbooleanfalsenoSend a visitor arriving on a small screen to the mobile front end instead of rendering the full console. Turn it on only where core/ai-agent/agenta-web-mobile is also deployed and routed, since the console cannot tell whether it is.
allow_embeddingbooleanfalsenoAllow this console to be rendered inside a frame on another site. Left off, a browser refuses to frame it.

Dimensionamiento del operador

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

NombreTipoPredeterminadoObligatorioDescripción
portinteger (min 1024, max 65535)3000noPort the front end serves on; the ingress tier connects here. Most operators should omit this and let the Recipe assign the default (3000).
external_base_urlstring—noExternally reachable base URL of the whole platform, as a browser reaches it through the ingress tier — for example https://agenta.example.com. The browser calls this rather than any in-cluster Service name, which does not resolve outside the cluster. The compiler cannot know a cluster's external hostname, so this carries no default and the Kubernetes realization halts at build until it is set.
engine_versionstringv0.114.1noConsole container image tag. It tracks the same release as the rest of the platform, so a Release moves them together.
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 browser console. The ingress tier points its upstream at this name rather than at any of the platform's API tiers.
portinteger—síTCP port that Service serves the console on. It follows the port an operator set in the Release, so the ingress tier reads it rather than assuming a default.
endpointstring—síFull in-cluster base URL of the console, with the host and the port already composed. It is the upstream a gateway forwards browser traffic to, not the address a browser types.
protocolstring—noURL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`.

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.

api

Selector
component.aggrega.ai/category=ai-agent
Inyección
env

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

services

Selector
component.aggrega.ai/category=ai-agent
Inyección
env

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

auth_core

Selector
component.aggrega.ai/category=security
Inyección
env

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

SlotSelectorObligatorioInyecciónSensibleDescripción
credentialfeature.aggrega.ai/kind=secretnoenvsíAPI key presented to the authentication core this connection reaches. Where a key is attached to the core, the same one is attached here. Unattached, no key is sent.

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
auth_keyfeature.aggrega.ai/kind=secretsíenvsíRequired key the platform signs its own internal tokens with. It carries the same value as the control-plane API's slot, because the tokens this front end presents are the ones that service verifies. There is no default: the build halts when nothing fills this slot.
crypt_keyfeature.aggrega.ai/kind=secretsíenvsíRequired key stored credentials are encrypted under. It carries the same value as the control-plane API's slot. There is no default: the build halts when nothing fills this slot.

Lista de permitidos de autoinyección

env

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