Skip to main content
An Administrator opens Connectors → Connect → Discord, chooses Install Discord Bot, and approves it for the intended server. The install flow links the installer’s Discord account to the Nuphos workspace.

​
Enable a channel

Run /nuphos enable in the channel you want to use, then @mention the bot with a task. Nuphos replies in a thread; later messages there continue the same agent session. Installing the bot alone does not enable every channel. Other members must link their own identity using Link Discord Account in the connection flow. Each person’s turns use that member’s Nuphos permissions and selected credentials. An unlinked identity is not the installer’s authorization.

​
Permission modes

Discord turns initially use Full Access for a member without an existing mode preference in that conversation. A linked member can use /nuphos auto or /nuphos full-access for their own turns. See permission modes. Do not assume an unattended thread will pause before every write or present the same plan cards as Desktop or Slack.

​
Files and verification

Try a simple read-only question in an enabled channel before production work. Attachments can go to and from the agent within the service’s size limits; when a file is too large, use its Nuphos download instead. Consider who can read the Discord thread before returning private data. If there is no response, check installation, enabled channel, the sender’s member link, runtime availability and the relevant connector access. Removing a link or server connection does not erase messages already posted to Discord.