The pattern most teams reach for first: a chat bot that wraps an agent. Discord and Telegram are real, built-in channel adapters - the user messages the bot, the message becomes the goal, the agent answers. No custom bot code, no webhook plumbing, the runtime ships the channel provider. (Slack itself isn't a built-in inbound channel today - if you also need to post into Slack, the pieces integration handles that as an outbound action.)
1runtime:2 mode: background3 entry_agent: helper45tools:6 modules:7 web: {}8 channels:9 config:10 providers:11 discord_bot:12 adapter: discord13 credential: { scope: per_user, provider: discord }14 activation: { agent: helper }1516agents:17 - id: helper18 modules: [{web: [search, fetch]}]19 brain: { provider: anthropic, model: claude-haiku-4-5, credential: { ref: anthropic_main, scope: per_user, provider: anthropic } }20 system_prompt: "Answer concisely. Cite sources."# 1. install runtime
curl -sSL https://digitorn.ai/install | sh
# 2. save the YAML above to ~/.digitorn/apps/my-slack-bot/app.yaml
mkdir -p ~/.digitorn/apps/my-slack-bot
# paste the YAML into app.yaml
# 3. deploy
digitorn deploy my-slack-botEngineering notes from the Digitorn team. No marketing, no launch announcements, no "10 prompts that will change your life". Just the things we write that we'd want to read.