---
title: "Create, Configure, and Run an Agent | Agent Barn"
canonical: "https://agentbarn.dev/guides/agent-lifecycle-and-configuration"
pubDate: "2026-08-25T00:00:00.000Z"
updatedDate: "2026-08-29T16:41:32.000Z"
author: Agent Barn
description: "Understand agent creation, lifecycle states, configuration updates, safe restarts, and deletion behavior."
tags: [Product guide, Agent operators, Agent Barn]
categories: [Guides]
---

# Create, Configure, and Run an Agent

An Agent is created with a pinned Template version, selected Skills, platform credentials, and explicit creator access. Configuration is applied deliberately, and running Agents restart when a runtime-relevant change must take effect.

## Guide details

- Reference: GD-02
- Type: Product guide
- Audience: Agent operators

## Choose a supported Runtime and Platform

Runtime and chat Platform are separate choices. Hermes supports Slack, Telegram, and Discord. OpenClaw supports Slack, Microsoft Teams, Telegram, and Discord. The API validates each pairing, and the Platform cannot be changed through a normal Agent update.

## Understand the lifecycle

Slack and Discord Agents start in `STOPPED`. Teams and Telegram Agents attempt to start during creation and become `RUNNING` or `ERROR`. `STOPPED` and `ERROR` Agents can be started; `RUNNING` Agents can be stopped. Deletion soft-deletes the Agent after removing runtime resources.

- Start rebuilds runtime resources, renders the pinned Template, and creates a fresh Ingest key.
- Stop snapshots logs before removing active runtime resources.
- A successful start clears a prior error; invalid repeated transitions return a conflict.
- Deleting a Slack or Discord Agent releases its bot token for reuse.

## Apply configuration safely

The configuration page groups Profile, Template, platform routing, Skills, keys and integrations, Agent-owned overrides, and the Danger zone. A stopped Agent uses Apply and remains stopped. A running Agent uses Apply & Restart for runtime-relevant changes. Secret changes require separate credential-management permission, and plaintext is never returned.

## Shared-channel behavior

Agents require an explicit mention in shared channels and groups. Slack requires a fresh mention on every message, including later thread messages. Direct messages are exempt. Mention policy is generated at start, so restart an Agent after changing applicable configuration.

## Before you start

Verify the Template requirements, assigned Skills, provider credentials, routing allowlists, model, approval mode, and intended access. Test one representative request in an allowed destination and one request outside the allowed boundary.