Enable and run
New agents are disabled. Enabling is the deliberate step that makes an agent runnable.
What enabling does
For an owned agent or independent clone, Aleph pins the reviewed immutable bundle version, synchronizes its schedules, and activates connected channel transports. An installation instead follows the source owner’s current enabled harness; your enable/disable state still controls whether it runs. Chat, scheduled turns, and memory writes are allowed only while the agent is enabled.
Before enabling, open the agent Overview and verify the bundle version. The configuration readiness checklist shows required vault secrets, environment variables, and Connections that still need attention. Select an incomplete row to open the matching configuration page, then return to Overview. Owned agents and clones can enable the version you reviewed; installations enable the installation itself.
The Overview distinguishes the version you are inspecting from the runtime version. If you inspect a different version while an owned agent or clone is enabled, Aleph keeps the current live version pinned until you explicitly switch it. For installations, the version menu is read-only inspection and never changes the source harness they follow.
Run the agent
Once enabled, you can:
- start or resume a web conversation;
- run a schedule immediately;
- let hourly schedule evaluation launch due work;
- receive messages through connected Discord or Telegram bots.
Every turn reconstructs the selected runtime bundle in isolated compute and resumes the selected conversation's runtime session.
Disable safely
Disabling removes active schedules and blocks new runs. Existing conversations, versions (including memory files), and channel bindings remain stored. Inbound channel events are skipped until the agent is enabled again.
Publishing a newer version does not silently change a running owned agent or clone. Enable the version you want to pin. Installations pick up the source owner’s newly enabled harness on their next run.