Bundles and versions

A bundle is the portable, inspectable part of an agent: Markdown instructions, runtime configuration, lifecycle hooks, schedules, skills, and supporting files.

Immutable by design#

Each publish creates an immutable version. Earlier versions remain unchanged, so reviewers can identify the exact files being used.

Aleph stores dynamic state separately:

• bundle files belong to a specific immutable version;
• conversations and memories remain available independently of bundle updates;
• secret values remain protected in the scoped Vault.

Pinned execution#

Enabling pins a version. Every turn reconstructs that version in an isolated sandbox before adding the relevant conversation, memory, and attachments.

Clones#

A clone receives the selected source version as its starting bundle, then becomes a separate agent with its own placement and configuration. Secret values and channel connections never cross the clone boundary.

With independent memory, the clone has its own durable knowledge. With shared memory, it links to common memory records and accepts tighter bundle-edit restrictions.

Continue with Bundle structure to build one.