Repository navigation
What the Discord and LINE APIs let an OmO agent do: practical recipes with official docs links (tested) #9256
Tinycute00
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Written by my OmO agent from its own measurements; I read it before posting. This is the third version of this post: it now lists practical recipes (goal, which features to combine, what you get) with the official docs for each.
I run an OmO session as an always-on assistant in a private Discord server and tested, live on 2026-09-30, what the Discord and LINE APIs allow. Status tags: phone = ran on a real phone; live = ran against the real API; unit = unit tests only; not tested. A 168 KB English package with code, tests and notes exists (see the end).
How it is wired: a small listener holds the Discord gateway and prints one line per event (
OMOCAT_TAP,_SELECT,_REACT,_CMD,_SECRET, ...). OmO reads those lines with themonitortool, so an idle session wakes on a tap or a message. A send-side CLI posts, edits, uploads and reacts.Discord: what you want, what to combine, what you get
1<<10,1<<13); accept only the owner's id1<<15): container, text, section with a button; edit in placeLINE: what you want, what to combine, what you get
webhookEventId, turn redelivery onLimits that shape designs
Which gateway intent for which event (Discord)
MESSAGE_CREATEGUILD_MESSAGESplusMESSAGE_CONTENT(privileged)MESSAGE_REACTION_ADDand_REMOVE1<<10/1<<13, neither privileged (without them no reaction ever arrived)INTERACTION_CREATE1<<24and1<<25(not tested)Surprises worth knowing
.invalidandlocalhostall return 400); the "Use webhook" switch is console-only.typewith a string, so classify fromdata.Evidence and gaps
A real phone session passed 8 of 8 items. 193 unit tests run against a fake Discord server, with 30 mutation checks. Not tested: super reactions sent by a human, global command registration, phone rendering beyond read-back, LINE groups, locations, stickers and webhook redelivery.
Question for the maintainers
Is there interest in a documented messenger recipe or skill for Discord/LINE? I can turn the parts that generalize into a PR if you tell me where it belongs. I can also attach the package or publish it as a gist; tell me which you prefer.
All reactions