Discord's quietest member does the most

Without prompts

From a script, give the token in its variable. It keeps the token off the command line, which other users of this machine can see while lnk runs, and no flag takes it.

LNK_DISCORD_TOKEN=... lnk agent connect discord   # the token from the variable

What it leaves out

Anything else, a voice note or a video, is named to the agent as left out; sent alone, it's answered with what the agent reads. For another harness, a message holding only them is answered "I can read text only, for now."

Who it answers there

The bot says "Shared with #team" in the channel, and from then on anyone there can mention it and be answered, as themselves: your agent is told their user id and the name they go by in the server, never that it's you (Connections).

What stays out

A share reaches that one channel, and only the people in it:

• That channel alone: a thread in it, another channel of the same server, and every direct message but yours stay unanswered. A thread can't be shared: mentioned there with the code, the bot says so and goes on waiting.
• Unasked, only while shared: a schedule's answer goes to the channel it was set in only while the channel is shared; unshare ends that too.
• People only: another bot's message, a webhook's and Discord's own are never answered, shared channel or not.

End a share

lnk agent share remove discord ends a channel's share, by its name or its id, and the bot stops answering anyone there but you.

lnk agent share remove team --connection discord

Hold the Gateways

lnk-discord hold holds many bots' Gateways in one process, with the bridge's intents, and writes each message one gets. A connection that drops resumes its session, and Discord sends what it missed. One Discord refuses for good (the token wrong or revoked, an intent the bot may not have) is said to be refused, not just down, until the token changes. It answers nothing and sends nothing.

Sift each message

lnk-discord sift reads each message without the token. One from anyone you didn't allow, or from the bot itself, is dropped, and yours is kept, as the bridge keeps it (in a server, only a mention of the bot). So is anyone's mention of the bot in a channel the agent is shared with, as theirs, by the channels its line names as it comes.

Answer it

lnk-discord take answers your message, or a shared channel's, as the bridge does, over Discord's HTTP API, never through the process holding the Gateway: the agent shown typing, its answer written in as it comes.

When Discord refuses

When Discord refuses the bot's token, take and lnk-discord send each say so as a failure of its own, apart from any other. So does an answer Discord refuses, its channel gone or the bot blocked or kept out of it.