Claude Code AFK Agent: Run Discord-Backed Autonomous Workers via Teams Plugin

A Reddit post details how to configure Claude Code to run as an AFK agentic system — reading Discord messages, spawning a single worker teammate per task, and reporting results — all without hitting programmatic API limits. The setup uses the official channels plugin and the built-in teams agent.
Setup
Enable the teams agent with environment variable:
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
Install and configure the official channels plugin:
/plugin marketplace add anthropics/claude-plugins-official
/plugin install discord@claude-plugins-official
/reload-plugins
Discord channel docs are available from Anthropic. Create a bot, add it to the channel, and assign the required permissions.
CLAUDE.md — Lead Agent Behavior
The provided CLAUDE.md defines the lead agent's role. Key rules:
- Lead does not do work. It listens, dispatches, and reports. If it starts reading files or running commands, it must stop and delegate.
- Never spawn more than one worker. Queue additional tasks on the shared task list instead.
- Acknowledge every Discord message immediately. React with emoji (
👀,✅,🤔,⏸,❌) and reply with a one-liner stating the next action. - Post status updates with a glyph (
starting,working,done,blocked,error), one line of context, and numbers if relevant. - Interpret terse messages liberally. Resolve references against the task list and recent channel context. If ambiguous, ask one short question.
Failure Handling
- If a worker stops responding, check the shared task list and mailbox. If both stale, ask the worker to shut down, then spawn a replacement with a resume-from-last-checkpoint instruction.
- Worker silent for over an hour on a single message: force shutdown. Post
⚠️ worker silent 60m, force-shutting downto Discord, terminate the teammate, and ask the user whether to respawn or abandon. - If the lead drifts into doing work, delete partial output and spawn a worker to do it properly.
- If multiple requests queue up, post the queue to Discord so the user can reorder.
Who It's For
Developers who want a persistent, Discord-controlled agent that runs autonomously without exceeding programmatic rate limits.
📖 Read the full source: r/ClaudeAI
👀 See Also

Developer tracks frustration with 'F-Bombs Per Thousand Prompts' metric across 44,212 Claude Code logs
A developer tracked 'fpk' (f-bombs per thousand prompts) across 44,212 Claude Code prompts over 5 months, finding frustration dropped 3.4× from Claude Opus 4-5 to 4-7, and most cursing targeted environmental tooling, not the model.

Multi-operator Claude Code: Hub-based architecture for multi-agent sessions
A hub-based setup for Claude Code enables multiple people to attach to the same session, route subtasks across repos, and run headless agents in Docker containers.
Mesh LLM: Distributed AI Computing on Iroh – Run LLMs Across Your Own GPUs
Mesh LLM pools GPUs you already have across machines and exposes them as one OpenAI-compatible API. Distributes models locally, via peer routing, or as a pipeline across several nodes using iroh's QUIC transport.

LLM Architecture Gallery: Visual Reference for Model Designs
Sebastian Raschka's LLM Architecture Gallery collects architecture figures and fact sheets from The Big LLM Architecture Comparison and A Dream of Spring for Open-Weight LLMs, with detailed specs for models like Llama 3 8B, DeepSeek V3, and Gemma 3 27B.