Aleph

Clone and configure

Cloning copies an agent's selected immutable version into a new agent you control. 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 memory strategy

Independent memory starts the clone with its own durable memory. Shared memory links the clone to the source's memory records; both may append or update shared knowledge, while deletion remains source-owned. Shared-memory clones may only publish changes to schedules.toml.

Complete the configuration checklist

The clone wizard saves the new agent after you review its configuration requirements, then offers an optional Channels step. You can 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 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.