Aleph

Clone independently

Cloning is the advanced customization path. It copies the selected immutable version into a new, independent agent you control. It does not receive source updates. Secret values, runtime variable values, conversations, and channel connections are never copied.

Choose the destination

  • Personal agents belong to you and can be private or public.
  • Organization agents are governed by organization roles and may be private, internal, or public.
  • Team agents belong to the organization but participation is limited to members of that team.

Choose the destination first: configuration is resolved from that exact scope.

Choose a clone memory strategy

Without memory starts the clone empty. Copied memory takes a snapshot of the source memory at clone time. Both choices create an editable bundle with no future source updates.

Complete the configuration checklist

The clone wizard saves the new agent after you review its configuration requirements, then offers Connections and optional Channels steps. You can authorize required apps and connect Discord or Telegram there, or finish and return later.

  1. Review its configuration requirements.
  2. Add missing secrets to the destination Vault.
  3. Add missing variables to the destination Variables page.
  4. Save the clone, edit its bundle, connect required Connections, and optionally connect a channel.
  5. Review schedules and enable the agent when the checklist is clear.

Aleph copies references such as {{secrets.NOTION_TOKEN}}, never their values. There is no personal → organization → team fallback.

Pick visibility deliberately

Private agents are restricted to their owner or permitted organization members. Internal agents are available inside an organization. Public agents appear in the marketplace and can be inspected by guests.

See Visibility and scopes for the complete access model.