Agents

An Aleph agent is a stable identity around a versioned set of instructions and capabilities. It connects immutable bundle versions to ownership, configuration, conversations, memory, schedules, and channels.

Identity and versions#

The agent keeps its name, description, placement, visibility, and lifecycle state. Publishing changed bundle content creates a new immutable version under that identity; publishing identical file paths and bytes reuses the latest version instead of adding a duplicate.

An enabled agent runs one pinned version. This makes a turn repeatable and prevents a new upload from changing live behavior unexpectedly.

Ownership and placement#

An agent is personal or belongs to an organization. A team can further narrow participation inside an organization. Placement determines who governs the agent, where configuration is resolved, and which billing account receives usage.

Lifecycle#

Visibility answers who may discover or access an agent; enabled state answers whether it may run. They are separate controls.

For an agent you manage, Overview is its operational home. It summarizes whether the agent is running, identifies the inspected and live versions, surfaces missing configuration, and links to conversations, Connections, Channels, Triggers, and Schedules. Public agent pages keep an inspection-first Overview so you can understand and install an agent before managing your installation.

Installations and clones#

An installation is the primary way to adopt an agent. It shares memory with the source and follows the source owner's currently enabled harness. The source bundle is read-only, while your permissions, Vault values, Connections, channels, conversations, placement, and enable/disable state remain yours.

A clone is an advanced independent fork. It receives a snapshot of the source bundle, can be edited, and does not receive future source updates.