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.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:17af94a055b8d65143e7fee39c6fd1175ab797755eff9c1f3490361acacfda2c
Published
2026-11-10T10:07:28Z
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:909b18db4cb215f839167d32e492fc4f7bc55d4b2539f116ba04b03b5a0a38ea

Reference at this version

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

Developer parameters

Values the developer sets in the Aggregate.

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

Operator sizing

Infrastructure sizing the operator tunes per environment.

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

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesIn-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—yesTCP 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—yesFull 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`.

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.

api

Selector
component.aggrega.ai/category=ai-agent
Inject
env

This socket declares no attachment slots, so a connection through it carries no attachment.

services

Selector
component.aggrega.ai/category=ai-agent
Inject
env

This socket declares no attachment slots, so a connection through it carries no attachment.

auth_core

Selector
component.aggrega.ai/category=security
Inject
env

Slots each connection through this socket may fill

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

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.

SlotSelectorRequiredInjectSensitiveDescription
auth_keyfeature.aggrega.ai/kind=secretyesenvyesRequired 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=secretyesenvyesRequired 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.

Self-inject allowlist

env

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