What’s inside an Aleph agent bundle?

An Aleph agent is not an opaque prompt hidden behind a button. Its behavior begins with a versioned bundle you can inspect before you clone it.

The bundle holds durable instructions and may declare sandbox behavior, schedules, hooks, skills, and references to required configuration. Secret values do not belong in it. Aleph resolves those separately from the vault of the person, organization, or team running the clone.

Published versions are immutable, so an enabled agent can pin exactly what it runs. Conversations and memory remain outside the bundle as live runtime state.

The result is a useful boundary: creators can publish portable agent behavior, while adopters keep control of identity, configuration, and data.