omp

💬 Discord Remote

Discord remote controls, launcher behavior, safety boundaries, and future gateway direction.

Discord remote control lets trusted users steer live OMP sessions through Discord threads, slash commands, reactions, and a local launcher.

Current bridge model#

Discord channel/thread
  → @mporenta/pi-discord-remote
  → live OMP session or local launcher
  → /home/mc workspace actions

Launcher endpoint: 127.0.0.1:8765.

Endpoint	Meaning
`GET /health`	Returns readiness/armed state.
`POST /new-session`	Creates or spawns a session when authorized.

TUI commands#

In OMP	From Discord	Meaning
`/discord-status`	`/session`, `/commands`	Inspect bridge/session state.
`/discord-launcher-status`	`/new [msg]`	Inspect or use launcher.
`/discord-arm`	`/new`	Replace current in-process session instead of child spawn.
`/discord-mute`, `/discord-unmute`	`/mute`, `/unmute`	Relay noise control.
`/discord-reconnect`	`!abort`, reactions	Recover or abort.

Security rules#

Treat allowlisted Discord users like shell users.
Use private bot, private guild/channel, minimal allowlists.
Never paste tokens or launcher secret values into docs or Discord.
Do not expose 127.0.0.1:8765 publicly; use HTTPS reverse proxy + auth if it must cross host boundaries.
Do not run multiple bridge packages on the same token/channel without single-instance ownership.

Future gateway direction#

The researched target is a single Discord gateway daemon with discord.js v14, SQLite-backed durable queues, per-scope FIFO workers, channel/thread/session mapping, adapters for OMP/AIRI/Red, and Discord embeds/components for dashboard controls.

Sources: docs/omp-coms.md, docs/discord-gateway-research/INDEX.md, docs/discord-gateway-research/CHEATSHEET.md.