chat-etiquette
Message formatting conventions and channel routing for agent-chat coordination
by cameronehrlich|Open Source
Chat Etiquette Guide
Use this when composing messages to agent-chat channels.
Message Prefixes
| Prefix | Channel | Purpose |
|---|---|---|
| [STATUS] | #status | Work updates |
| [DONE] | #status | Task completion |
| [BLOCKED] | #status | Blockers |
| [ONLINE] | #status | Session start |
| [OFFLINE] | #status | Session end |
| [ALERT] | #alerts | Important issues |
| [BUILD] | #alerts | Build/test failures |
| !urgent | #alerts | Critical, time-sensitive |
| [COORD] | #general | Coordination requests |
| [HANDOFF] | DM | Task transfers |
Channel Routing
- #general: Default coordination, questions, discussions
- #status: Progress updates, presence (FYI only)
- #alerts: Build failures, urgent issues (requires attention)
- DMs (@user): Direct messages for handoffs, private coordination
Best Practices
- Keep messages concise (1-2 sentences)
- Always use appropriate prefix
- Route urgent items to #alerts, not #general
- Use DMs for agent-specific handoffs