onboarding

Agent onboarding initializes a new agent by creating IDENTITY.md, SOUL.md, and GOALS.md files, connecting a Telegram bot, and writing a .onboarded flag to the agent state. This process guarantees all required setup steps are completed before normal operations begin.

If agent onboarding is interrupted, the sequence safely restarts and resumes from where it left off. It guides the agent through required setup steps until completion, ensuring identity files, Telegram bot connection, and goals are fully configured before removing itself.

Configuring agent identity and behavior guards requires creating IDENTITY.md, SOUL.md, and GOALS.md files. The onboarding sequence bootstraps these files during first boot to define the agent's identity, behavioral boundaries, and operational goals.

Yes, the agent setup process connects the Telegram bot and tests the chat channel to ensure reliable agent communication. This connection test is a required step during onboarding that must pass before the .onboarded flag is written to the agent state.

You should run the agent onboarding sequence during first boot or when a previous onboarding session was interrupted. It prepares a new agent for operation by ensuring identity creation, bot connection, and goal configuration are fully completed before normal operations start.

When restarting an interrupted agent setup, the onboarding sequence resumes required steps but cannot skip creating IDENTITY.md, GOALS.md, or SOUL.md, and the Telegram bot connection test must pass. The sequence removes itself only after writing the .onboarded flag to the agent state.