Component

core/ai-agent/phidata

A Phidata agent, run in-cluster as an application image the Release supplies. Phidata separates two kinds of remembering that other frameworks fold together: session storage, which holds the running conversation so a later turn can see an earlier one, and a knowledge base, which holds reference material the agent retrieves from. This component declares both as distinct topology edges — the only agent here that does — and its two values govern whether prior turns are replayed into the prompt and whether replies are formatted as markdown. The Release supplies the image containing the Phidata application. The catalog pins no image, so nothing renders until the Release sets `infra.image`. The variables each connection is delivered under are defaults: an `inject:` block on the connection replaces them with the names the application reads, as variables or as files, and a store connection writing none refuses a store served over TLS alone or over HTTPS, since the application would be handed only its host and port. Neither store connection carries a credential, so a store that requires signing in cannot be reached through one. Its Recipes deliver each own value under a default variable name; the component's own `inject:` block takes `env` and `file` entries, and one reading a value alone replaces that value's default name.

Provenance

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

Reference at this version

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

Developer parameters

Values the developer sets in the Aggregate.

Extends BaseComponents#/schemas/BaseAgentParameter

NameTypeDefaultRequiredDescription
add_history_to_messagesbooleantrueyes—
markdownbooleantrueyes—

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
imagestring—noContainer image running the Phidata application code.

Output contract

Values this component publishes to consumers over the uses topology.

No output values declared.

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.

model

Selector
component.aggrega.ai/category in (ai-model, gateway), model.aggrega.ai/api
Inject
env, file

Slots each connection through this socket may fill

SlotSelectorRequiredInjectSensitiveDescription
credentialfeature.aggrega.ai/kind=secretnoenvyesOptional credential the agent presents to the model this connection reaches. When attached, the Recipe delivers it to the application as OPENAI_API_KEY (a Kubernetes secretKeyRef on helm, the inject pipe on compose); unattached, the application runs without an injected key.

storage

Selector
component.aggrega.ai/category=datastore
Inject
env, file

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

knowledge_base

Selector
datastore.aggrega.ai/engine in (vector, semantic-memory, search)
Inject
env, file

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

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