Remote
Enables a stacks users with the ability to talk to their accounts from anywhere.
Remote lets a user chat with their stack’s account from the messaging apps they already use (Telegram, Discord, Slack, and WhatsApp today), with more providers added by writing a single adapter. A Remote is your stack, projected into a conversation.
Internally a Remote is an agent with trigger_type = "channel" scoped to one user. This matters because it means Remotes inherit everything agents already get: rate limits, execution records, metrics, enable/disable, deletion, stack level permissions.
Providers
- Telegram: Create a bot with
@BotFather, paste the token. Done. No public URL needed. - Discord: Create an application in the Dev Portal, enable the
MESSAGE_CONTENTintent, copy the bot token. Bots in >100 servers need Discord verification; the UI surfaces this inline. - Slack: Create a Slack App, enable Socket Mode, grant the required bot scopes (
chat:write,app_mentions:read,im:history,im:read,im:write), install to workspace, paste both tokens. - WhatsApp: Register a Meta app, add a phone number, set your stacknet node’s public URL as the webhook (Meta requires public HTTPS), and paste access token + phone number ID + verify token.
Last updated on