Skip to content

IRC and Twitch

  1. Choose a network and a bot nick. Register it with the network’s NickServ if required.
  2. Open Settings › Channels › Add channel › IRC. Enter the server (ircs:// for TLS), nick and password if needed.
  3. Send a private message to the bot and enter its code in This is my IRC to link your own nick.
  4. Under Rooms, list the channels the bot should use and choose their answer mode.

A nick is not proof that the owner wrote a request. Keep risky approvals in APX; do not assume NickServ makes an IRC message equivalent to a signed-in APX session. If the bot cannot join, check server scheme/port, nick availability, network authentication and the room list. Do not put a password into a public channel to troubleshoot.

  1. Create an account for the bot or choose the account that should speak.
  2. Obtain a chat token for that account with chat:read and chat:edit scopes.
  3. Open Settings › Channels › Add channel › Twitch. Enter the bot login, token and target channel.
  4. Add the channel’s chat under Rooms. A connected account without an allowed room is not enough.
  5. Start with When called and mention the bot to verify a reply in the public chat.

Twitch chat is a room, not a direct-message inbox. APX posts from the configured bot account. Check token scopes, login and room configuration when a bot connects but stays silent; platform moderation and chat restrictions still apply.

For each listed room choose Always, When called, When useful or Read only. Configure bot names, public knowledge, rules and rate limits before using automatic replies. Start narrowly: “Answer only questions about our published support hours; otherwise stay silent.”

Rooms outside the list are not read. A room’s participants do not gain your files or memory, even if you write there. The optional Search the web setting allows only public-web research, not your private tools. A read-only room is still public input, not owner authorization. See the room guide.