🤖 Discord.py × OMP Plugin Cheat Sheet
Bridge a discord.py bot (Python) with the OMP coding agent extension system (Bun/TS) — from zero to full bidirectional integration.
🧠 Core Concept
OMP extensions = TypeScript/Bun. discord.py = Python. They’re separate runtimes. You bridge them via one of three tiers:
|
🪝 Tier 1: Webhook |
🔧 Tier 2: MCP Server |
🌉 Tier 3: Extension + Bot |
| Direction |
OMP → Discord only |
Both (LLM invokes tools) |
Both (event-driven) |
| Needs Python? |
❌ No |
✅ Yes |
✅ Yes |
| Needs Bot Token? |
❌ No (webhook URL) |
✅ Yes |
✅ Yes |
| Discord → OMP? |
❌ |
❌ |
✅ |
| Auto-notify events? |
✅ |
❌ |
✅ |
| LLM calls Discord? |
❌ |
✅ |
✅ |
| Setup time |
~5 min |
~15 min |
~30–60 min |
| Deps |
None |
discord.py, mcp |
discord.py, aiohttp |
⚡ OMP Extension Contract (All Tiers)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
// ~/.omp/agent/extensions/my-ext/index.ts
import type { ExtensionAPI } from "@oh-my-pi/pi-coding-agent";
export default function myExt(pi: ExtensionAPI) {
// ── Registration Phase (sync) ──
pi.setLabel("My Extension");
pi.on("agent_end", async (event, ctx) => { /* ... */ });
pi.on("session_start", async (event, ctx) => { /* ... */ });
pi.registerTool({ name: "my_tool", /* ... */ });
pi.registerCommand("my-cmd", { /* ... */ });
// ⚠️ CANNOT call pi.sendMessage() during load — only in handlers
}
|
📡 Key Lifecycle Events
1
2
3
|
session_start → input → agent_start → turn_start
→ tool_call → tool_execution_start → tool_execution_end → tool_result
→ turn_end → agent_end → session_shutdown
|
| Event |
Use Case |
Return |
agent_end |
“Done” notification to Discord |
— |
tool_call |
Audit / block dangerous ops |
{ block, reason } |
tool_result |
Redact secrets before logging |
{ content } |
session_start |
Init bot connection |
— |
session_shutdown |
Cleanup / final flush |
— |
🪝 Tier 1 — Webhook (Zero-Dep, 5 min)
No bot. No Python. Just fetch(). OMP → Discord one-way.