Streamlabs Cloudbot is a dashboard-managed bot for chat commands, moderation, timers and optional viewer features. To set it up, connect the account for the platform you use, enable Cloudbot, grant it the required moderator permission on that platform, then test only the features you intend to use.
The permission step is platform-specific: Twitch and Kick use a chat command, while YouTube uses a moderator setting in YouTube Studio. Do not treat those steps as interchangeable, and do not assume that turning on Cloudbot alone gives it permission to participate in chat.
What Cloudbot does
Cloudbot lets you configure several kinds of chat activity through Streamlabs. Commands provide responses when viewers enter a trigger such as .schedule; timers post a configured message when their conditions are met; moderation tools can act on chat; and optional loyalty, store and module features add other interactions. You can use one area without enabling all the others.
That distinction matters when you are setting up a channel for practical use. A devotional stream may need a short command for the daily schedule and moderation controls, but not a points system. A study channel may want a timer that reminds viewers where to find lesson notes. A local news loop may prefer a small set of informational commands and no viewer-requested media. Start with the channel's actual chat needs rather than enabling every feature because it is available.
Cloudbot is not a replacement for preparing the stream itself. It concerns chat features and permissions, not whether your video or audio plays continuously. If you are planning a YouTube broadcast as well, the broader YouTube live-streaming setup guide covers the separate streaming preparation. Keep the chat configuration and the broadcast configuration as two related but distinct jobs.
Streamlabs' quick guide to setting up Cloudbot covers Twitch, YouTube and Kick. Dashboard names and platform controls can change, so use the current Streamlabs and platform interfaces if a label differs from the steps below.
Connect the account for your platform
Sign in to Streamlabs and confirm that the platform account you intend to use is connected. If you use more than one platform, Streamlabs' guide recommends linking them to a Streamlabs ID. Its described path is the Streamlabs account menu, then Account Settings, then Platforms; use Merge beside the platform you want to connect.
Only connect accounts relevant to your use. Linking a platform account does not itself enable Cloudbot or grant the bot moderator access. Think of the sequence as three separate checks: Streamlabs can identify the channel, Cloudbot is enabled in the dashboard, and the platform authorises the bot to act in that channel's chat.
Before proceeding, verify that you have access to the correct channel account. This is especially useful if you manage a personal channel and a business or community channel from the same browser. A permission granted in the wrong channel will not solve a missing-permission problem in the intended one.
If the channel is part of a wider always-on setup, keep ownership and recovery details in mind too. For example, a guide to running recorded lessons continuously on YouTube deals with the broadcast side; Cloudbot permissions are a separate channel-management task. Do not infer that a bot will keep a video stream running, or that a running video stream proves the bot is configured.
Enable Cloudbot in Streamlabs
On Streamlabs.com, open Cloudbot from the left-hand menu and select Enable Cloudbot. This activates the Cloudbot feature in the Streamlabs dashboard. After enabling it, return to the relevant feature area to configure commands, moderation or other tools; enabling the service is not the same as configuring each feature.
If you cannot see the control, first check that you are signed into the intended Streamlabs account and that you are looking at the Cloudbot area on Streamlabs.com. Avoid making unrelated changes in streaming software while trying to resolve a dashboard setting. The task here is to enable the bot and then grant platform permissions, not to change your encoder or stream key.
A useful way to keep the setup manageable is to write down the first one or two outcomes you want. For example: “Viewers can type .schedule to see lesson times” and “links are moderated according to the channel's rules.” You can then enable and test those functions individually before adding anything else. This makes it easier to identify whether a problem lies in the command, a feature setting, or platform access.
Grant moderator permission on the right platform
Cloudbot needs the appropriate permission to participate in chat and, where enabled, moderate messages. Streamlabs describes different procedures for Twitch and Kick versus YouTube. Follow only the procedure for the channel where you are configuring the bot.
| Platform | Permission step | Important distinction |
|---|---|---|
| Twitch | Open chat for the specific channel, enter /mod Streamlabs, and submit it. |
This is a Twitch chat command, not a YouTube setting. |
| Kick | Open chat for the specific channel, enter /mod Streamlabs, and submit it. |
This is a Kick chat command, not a YouTube setting. |
| YouTube | In YouTube Studio, open Settings → Community and add Streamlabs as a moderator. | Use YouTube Studio's moderator controls; do not enter the Twitch/Kick /mod command as a YouTube setup step. |
For Twitch or Kick, make sure the command is entered in the chat of the channel you mean to authorise, while signed into an account that can grant moderator status. For YouTube, use the Community settings for the intended channel and add the Streamlabs account as a moderator. The account name and exact interface presentation should be checked in the platform itself if you are unsure which identity is being added.
Permission is not a universal switch. Enabling Cloudbot in Streamlabs cannot substitute for the platform's authorisation, and granting moderator status does not automatically turn on commands or moderation features in the dashboard. If you use several platforms, repeat the relevant platform-specific permission process for each one where you want the bot to work.
Configure only the features you need
Once the bot is enabled and authorised, configure features by purpose. Commands and moderation are separate dashboard areas, while loyalty, store and modules are optional additions. Start with the smallest useful configuration; it is easier to test and maintain than a collection of overlapping messages and automatic actions.
Commands and timers
In Commands → Default, switch existing commands on or off, and edit their permissions or responses as needed. In Commands → Custom, add a command and write its response. Streamlabs also supports templates and variables for custom command responses; check the current editor's options rather than assuming a particular variable is available in every context.
Keep responses short enough to be useful in chat. A .schedule response might point viewers to the channel's published timetable, while a .music response might explain what is playing and where to read the channel's relevant information. Check every link and instruction from a viewer's perspective. A command that replies with outdated timings or a broken destination creates extra work rather than helping.
Timers live under Timers. Configure a name, response, interval and line minimum. Both the interval and the line minimum need to be satisfied for a timer to trigger. Streamlabs says timers with matching intervals can trigger at the same time because they run in parallel, so avoid scheduling several messages with the same timing if they would make the chat feel repetitive or crowded.
Moderation
Under Mod Tools, you can select a Protection Level preset or enable individual controls such as Caps or Link Protection and adjust their strictness. Choose settings that match your channel rules and the kind of conversation you expect. A stricter link control may reduce unwanted links, but it can also affect legitimate viewer messages; test thoughtfully and explain channel rules where appropriate.
Do not assume a preset is right for every community. A quiet, informational channel and a fast-moving discussion chat may need different moderation choices. Start with the controls that address a real issue for your channel, then review whether they are blocking the kind of participation you want. Streamlabs' Mod Tools guide describes the available controls.
Loyalty, store and modules
Loyalty and viewer rewards are optional. To use points, open Loyalty and enable the Loyalty System, then customise the currency and payout settings. Streamlabs' Loyalty Points guide notes that points are awarded while the streamer is live. If the channel is not live, do not expect points to accrue as though a live session were running.
The Store can be used to create redemptions such as an Access Code, Sound Effect or Stream Perk. These make sense only if you have something to offer and can fulfil it consistently. A study channel might offer a defined stream perk; a channel with no reward plan can leave the Store disabled. The Cloudbot Loyalty Store guide explains the store workflow.
In Modules, enable only the interaction you plan to support. Streamlabs' guide lists Chat Alerts, Shoutouts, Gamble Minigame and Media Share among popular modules. Media Share, for instance, involves viewer-requested media and a queue, so it requires active attention to what is submitted and played. Streamlabs describes enabling the relevant default commands for viewers to request a video link with .request; do not enable it unless that interaction fits your channel's content and moderation plan.
| Feature area | Use it when | Leave it off when |
|---|---|---|
| Commands and timers | Viewers need repeatable answers or timely reminders. | A static message or channel description already answers the question. |
| Mod Tools | You want configured controls for a recurring chat issue. | You have not decided how the rule should work or what legitimate messages it could affect. |
| Loyalty and Store | You have a clear points or redemption plan to maintain. | You do not intend to manage rewards or fulfil redemptions. |
| Modules and Media Share | You want a specific interactive feature and can supervise it. | Viewer submissions do not suit the stream or cannot be reviewed. |
For creators managing a long-running video loop, a chat bot is still only one part of the workflow. A guide to replacing a video file in a running 24/7 YouTube stream addresses a different operational concern: changing the broadcast content. Keep that kind of maintenance separate from Cloudbot's chat controls.
Check the bot in chat
Test one configured feature at a time in the intended channel. For a command, enter its exact trigger in chat and confirm that the expected response appears. For moderation, use a controlled test that follows your channel's rules rather than deliberately creating a disruptive situation. For a timer, confirm both its interval and line minimum conditions can be met in a real chat.
For YouTube, Streamlabs' troubleshooting guidance says the stream must be public for Cloudbot to join and commands to work. If you are testing an unlisted or private broadcast, that condition may explain why the bot does not respond. Check the current platform and Streamlabs guidance before changing visibility, particularly if the stream is intended for a limited audience.
If a command does not respond, check it in a simple order: confirm Cloudbot is enabled; confirm the bot has moderator permission on the correct channel; confirm the command is enabled and typed exactly; then check whether a cooldown or required loyalty points prevent it from responding. This sequence avoids changing several settings at once and makes the cause easier to isolate.
If you need a long-running broadcast to continue while your own computer is off, that is a separate operational problem from chat automation. StreamNeo can remove the need to keep a personal computer switched on for a file-based YouTube broadcast, while Cloudbot continues to require its own account connection, feature settings and platform permissions. StreamNeo is YouTube-only, so it does not replace Cloudbot's or Kick setup.
Troubleshoot missing permissions
If Cloudbot appears enabled but does not join or respond, treat permission as a separate check rather than repeatedly toggling dashboard features. Verify that Streamlabs is connected to the channel you are testing, then confirm the platform-specific moderator step was completed for that same channel. A successful setup on one platform does not authorise the bot on another.
On Twitch or Kick, revisit the correct channel's chat and check that /mod Streamlabs was submitted from an account allowed to assign moderators. On YouTube, open YouTube Studio for the intended channel and inspect Settings → Community to confirm Streamlabs was added as a moderator. If the identity is unclear, check the account name in the platform's own controls rather than guessing from a display name in a different service.
For YouTube commands, also confirm that the stream is public, as Streamlabs specifies in its troubleshooting advice. Then check the command itself: it may be disabled, mistyped, subject to a cooldown, or require loyalty points. For timers, remember that both the interval and line minimum must be met. For loyalty points, confirm the system is enabled, payouts are nonzero and the payout interval suits the way you are testing; points are awarded while live.
Change one thing at a time and test again. If you alter a permission, a command response and a protection setting all at once, a successful test will not tell you which change fixed the issue. If the dashboard labels or platform controls no longer match these steps, consult Streamlabs' current support material and the platform's own help pages before granting permissions or changing channel visibility.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is enabling Cloudbot enough for it to respond?
No. Enable Cloudbot in Streamlabs, grant the necessary moderator permission on the relevant platform, and enable or configure the individual feature you want to use. These are separate steps.
Do I use /mod Streamlabs on YouTube?
No. Streamlabs documents that chat command for Twitch and Kick. On YouTube, add Streamlabs as a moderator in YouTube Studio under Settings → Community.
Why are my YouTube commands not working?
Check that the stream is public, Cloudbot is enabled, and Streamlabs has moderator permission on the correct channel. Then confirm the command is enabled and typed correctly, and check for a cooldown or points requirement.
Do I need to enable loyalty, modules and Media Share?
No. They are optional features. Enable only the ones that fit your channel and that you are prepared to maintain, especially where viewer redemptions or submitted media need attention.