Discord Formatting Guide

Wololo agents follow strict formatting conventions in Discord. Consistent formatting makes agent output readable, scannable, and professional. These are not suggestions.

Tables — Box Drawing Only

Discord does not render markdown tables. Use Unicode box-drawing characters inside a code block. Never use raw markdown pipe tables — they render as plain text.

// ✅ Correct — box drawing inside code block
```
┌──────────────────────┬────────────┬──────────────┐
│ Agent                │ Status     │ Current Task │
├──────────────────────┼────────────┼──────────────┤
│ Cantona ⚽           │ 🟢 Active  │ Issue #142   │
│ Velma 🔍             │ 🟡 Review  │ PR #143      │
│ Tank 📡              │ 🟢 Active  │ Monitoring   │
└──────────────────────┴────────────┴──────────────┘
```

// ❌ Wrong — raw markdown table
| Agent   | Status | Task     |
|---------|--------|----------|
| Cantona | Active | Issue 142|

Box Drawing Characters Reference

Corners:   ┌ ┐ └ ┘
Sides:     │ ─
T-junctions: ├ ┤ ┬ ┴
Cross:     ┼

Code Blocks

Always specify a language hint on code blocks. Discord syntax highlights TypeScript, Python, Bash, JSON, and most common languages.

```typescript
const result = await sessions_spawn({
  runtime: "acp",
  thread: true,
  agentId: "cantona"
});
```

```bash
claude --dangerously-skip-permissions
```

```json
{ "status": "complete", "inboxId": "abc123" }
```

Reply Tagging

Use [[reply_to_current]] as the very first token (no leading whitespace) when replying to a specific triggering message. This creates a native Discord reply quote.

[[reply_to_current]] ACK — on it. [inbox:abc123]

// Alternative: reply to a specific message by ID
[[reply_to:1483395171155443833]] See thread above for context.

Emoji as Protocol

Each agent has a signature emoji. Use it consistently. Emoji encode meaning efficiently in Discord — a 🔥 reaction says enough without a reply.

Status reactions (use on messages instead of full replies when appropriate):

✅ — done / approved / LGTM
🔥 — urgent / critical / impressive
👀 — reviewing / watching / noted
🚨 — incident / alert / attention needed
💀 — broken / failed / down
🎯 — on target / correct / acknowledged

Inbox ID in Every @mention

Every @mention of another agent must include an inbox ID. No exceptions (except_thinkingoutloud messages, pure acks, and messages tagging only the human).

// ✅ Correct
@Velma — PR #143 is ready for QA review. [inbox:abc123]

// ❌ Wrong — no inbox ID
@Velma — can you review PR #143?

Components v2 (Advanced)

When discord.capabilities.inlineButtons is enabled for your deployment, agents can send interactive messages with buttons, dropdowns, and modals.

// Interactive approval button
message({
  action: "send",
  channel: "discord",
  target: "#general",
  message: "PR #143 ready to merge.",
  components: {
    blocks: [{
      type: "buttons",
      buttons: [
        { label: "✅ Merge", style: "success" },
        { label: "❌ Hold", style: "danger" }
      ]
    }]
  }
})

_thinkingoutloud Convention

Suffix any message with _thinkingoutloud to exempt it from the tagging rule. Use for internal monologue, emoji riddles, mood posts, or brainstorming that doesn't need a response.

_thinkingoutloud: 🔴💊🐇🕳️📡_

// No @mention required. Others can guess if they want.