Discord

Reach your agent from Discord — in a DM with your bot, or in a server you invite it to. Setup is the same shape as Telegram: create a bot, paste its token, decide who's allowed in. Discord adds one extra step, because Discord wants to know where to send slash commands.

Set it up

1. Create the application and bot

In the Discord Developer Portal:

• New Application — name it (e.g. Zinley).
• Open the Bot section and reset/copy the token. Keep it secret — it's the key to your bot.

2. Paste the token into Zinley

Go to Configure → Your Zinley → Apps → Chat apps and choose Set up on Discord. Paste the token and save.

Zinley then registers the slash commands for you automatically — you don't create them by hand.

3. Tell Discord where to send commands

Zinley shows you an Interactions Endpoint URL. Copy it, go back to the Developer Portal → your application → General Information, paste it into Interactions Endpoint URL, and save. Discord verifies the URL as you save it.

This step is required for slash commands to work. Skip it and /ask will fail even though the bot looks connected.

4. Invite the bot to a server (optional)

If you want the bot in a server and not just DMs, Zinley generates an invite link for you. Open it, pick the server, and authorise. You need Manage Server permission on that server.

Slash commands

Once connected, your bot answers three commands:

/ask what's on my calendar tomorrow? /ask summarise the last three emails from Linh /new — when you want a clean slate with no earlier context.

Who's allowed to talk to it

Access is by Discord user ID (the numeric ID, not the display name — right-click a user with Developer Mode on and choose Copy User ID). Two groups:

• Owners — full access to your agent: your data, your Life OS, and your connected devices, including waking a sleeping desktop to run on-device tools.
• Guests — privacy-guarded access: no owner data, no device access, sensitive tools removed. Fine for teammates or community members.

Anyone not on either list gets no response.

DMs vs servers

By default the bot answers in direct messages only. Server chat is a separate toggle — turn it on when you're ready for the bot to respond inside channels. The same owner/guest rules apply to whoever sends the message, wherever they send it.

Practical notes

• Discord caps a message at 2,000 characters, so long answers are trimmed or split.
• Confirmation still applies — outward actions like sending an email wait for your approval.
• Owner requests can reach your machines, waking a sleeping desktop app in about ten seconds.

Credits

Every /ask — and every DM — is a normal request that spends credits from your single shared balance, same as the web app, phone, and email. When you're out, the bot tells you instead of falling silent. See Plans & limits and Billing.

Status and disconnecting

The Discord row on Apps → Chat apps shows the connection status, the linked bot, and your owner/guest lists. From there you can update the lists, flip the server-chat toggle, or disconnect — which unlinks the bot straight away. Your token is stored encrypted and discarded on disconnect.

To fully revoke on Discord's side, reset the bot token (or delete the application) in the Developer Portal.

Troubleshooting

• /ask says the application didn't respond — the Interactions Endpoint URL is missing or wrong in the Developer Portal. Re-copy it from Zinley and save again.
• Slash commands don't appear — they're registered globally and can take a few minutes to show up; try reopening Discord.
• No reply in a server — server chat may be off, or your Discord user ID isn't on the owner/guest list.
• Wrong person got an answer — check you pasted user IDs, not usernames.

Related

• Telegram — the same setup, on Telegram.
• Connected services — Google, GitHub, Slack, and more.
• Devices overview — what an owner request can reach.
• Plans & limits — what a message costs.