Aleph

Bundle structure

An Aleph bundle is a folder of plain-text instructions, configuration, skills, and supporting files. Five root files are required.

Minimal bundle

my-agent/
├── AGENTS.md
├── README.md
├── sandbox.toml
├── hooks.toml
├── schedules.toml
└── skills/
    └── research/SKILL.md
  • AGENTS.md defines identity, behavior, and operating rules.
  • README.md explains the agent to people inspecting it.
  • sandbox.toml declares runtime settings and scoped environment mappings.
  • hooks.toml defines commands around each sandbox turn.
  • schedules.toml defines recurring prompts.
  • skills/ contains reusable capabilities following the Agent Skills convention.

All five root files are required, even when a TOML file has no entries. Additional safe relative paths are allowed; channels are configured in Aleph, not in the bundle.

Keep state out of the bundle

Bundles are immutable versions. Conversations, memories, uploaded files, configuration values, and channel credentials live in platform storage and are materialized only when needed.

Do not add secrets. Reference them from sandbox.toml with {{secrets.NAME}} instead.

Design for inspection

Use descriptive filenames, keep AGENTS.md focused, and place detailed procedures in skills. A reviewer should understand the agent's purpose and risk before enabling it.