Connect an AI assistant

What an assistant can do

Connect an AI assistant to your channel and you can build flows by describing them in a chat. Ask it for "a !hug command that hugs whoever you name" and it looks at what your channel already has, drafts the flow, checks it, tries it out without anything happening on stream, and saves it for you — switched off, ready for you to look over. It can also give the flow a short description of what it is for.

Help me connect Bloopbot to this assistant at https://bloopbot.com/api/mcp. Guide me through adding it as a custom MCP connector, signing in, choosing my channel, and allowing permission to see flows, create and edit flows, and run a flow as a test. Untick live switching and real runs unless I ask for them.
After connecting, verify it works by listing my flows and packs. Suggest a simple first flow, validate it and test it as a dry run. Show me the result before saving anything.

Not sure yet what you want? Say so, for example "help me make my stream better". Instead of guessing, the assistant asks you to choose what to make: flows (chat commands and automations), a simple overlay from Studio's ready-made widgets and themes, an advanced overlay with a custom code widget, or an overlay and flows together, such as an alert your viewers set off. It tells you if that choice needs a permission you didn't allow, then asks only what it still needs to know before it starts.

You can also ask it to arrange your public page, switch its pages on or off, update your links and gear, or choose one Google Font for all headings and another for body text. If you allow domain management, it can start connecting a domain you own and show you the DNS record to add.

You can ask it to group existing flows and overlays into one of your own packs, change their order, or rename a pack. It leaves each flow's live state and each overlay as they were. Putting an overlay in a pack needs the assistant to be allowed to see your overlays.

It can also make, change and delete your control panels, and put them in a pack you made. Build a control panel shows how.

If you allow it to create and edit flows, it can also make, edit and delete your groups, the sets of steps several flows share. Before it saves a group, it checks every flow that uses it. A change that would break one of them isn't saved, and the assistant tells you which flow it would break. A saved change reaches every flow using the group straight away, switched-on ones included. It can't delete a group while a flow still uses it, including a flow in your Trash.

It can add a Post to Discord step to a flow and write its message, embed and link button, for example to announce your stream in Discord. It can't see your connected Discord servers, so it leaves the server, channel and any role to mention empty. Choose them in the step yourself before you switch the flow on. It never adds a ping unless you ask for one.

It can build video request flows with Request a video, Skip the video and the Video request ended trigger, but approving a video stays with people: only you, your editors or a moderator can press Play on the Media share page.

It can add a Post to Bluesky, Post to Mastodon, Post to X, Post to Threads, Post to Instagram or Post to Facebook step to a flow and write its text, choose the picture and the link card, for example to announce your stream on social media. It knows the Socials pack already holds a go-live flow for each network, and it won't build a second one for a network that has one. It can't connect or disconnect your accounts, see which account is connected, install the pack, send a test post or add X balance: connect the network on Connections, then press Send test post in the step yourself. A go-live flow can't be enabled until its network is connected.

If you allow points store access, it can show your items, make a new one or edit one you already have. New items it makes start off sale. It can also inspect a wheel's segments to help plan a flow; wheel edits still happen in Studio and take effect when you Publish.

If you allow overlay access, it can create an overlay or a theme, inspect them and edit their Studio drafts, including picture frames round panels, chat lines and alert cards. It can start from Studio's ready-made layouts to build a matching set of gameplay, chatting, Starting soon, Be right back and Ending screens. It can show you a picture of each draft over sample stream content, make changes and show another picture until the design looks right. It can choose a file already in your media library, or upload a new picture, sound or video when your assistant can read the file you give it (in seconds, when your assistant can run commands on your computer), and it can put files into folders, label them with tags and delete the ones nothing uses to keep the library tidy. It can also place a layer on the vertical layout for Twitch's dual format and show you a picture of how it looks on a phone-shaped 1080×1920 canvas. Viewers see none of it until the draft is published: you review and Publish it in Studio yourself, or, if you allow it, the assistant publishes it for you once you've agreed.

The assistant can show you the kinds of layers Studio offers — including Chat, each alert type and Minigames — and explain their starting settings before you choose one. It can put a Clock, a Social rotator with your handles, an Event list of your latest follows, subs, gifts, cheers, raids and redemptions, a Clip player for your !so shoutouts, or a Media share player for the YouTube videos your viewers share on an overlay, and start a Label as a Viewer count or Follower count. Your saved overlays are a separate list, so you can name the one you want to change. In a theme’s alert designs it can also give an alert card the Free layout, placing its picture, title, subtitle and message where you ask, then show you a picture of the result. It can also move the whole Free card inside its layer with the design’s card X and Y offsets, without changing the layer’s placement. Custom alerts that draw the same design use the same arrangement.

An assistant can preview an optional new look for a built-in widget before changing it. For example, Now playing 2 keeps the song settings and groups the current track and queue in one panel. Ask to see the preview first; after you choose it, the change waits in the Studio draft until Publish.

It works with any assistant that can add a custom connector, sometimes called an MCP server: Claude, ChatGPT and Claude Code among them.

You can ask the assistant to add Turn flows on or off with several selected flows, or Turn a pack on or off to make a mode command or Run button. It can use your existing flows and packs, then test the switch without changing their live state. Switch packs from a flow explains what happens when the controlling flow runs for real.

It can also build flows that start from what OBS does, such as a chat message when you switch to your BRB scene, and flows that make OBS act, such as a mods-only !brb that switches scenes. It cannot list your OBS scenes or change OBS settings, so give it the scene’s name exactly as OBS shows it, and raise the overlay’s Page permissions in OBS yourself.

Let your assistant read a guide

You can ask an assistant to read Bloopbot’s public guides before helping you. This needs no sign-in or paid plan.

For an overview, give it Bloopbot’s agent guide. It links the public guides, current prices, authentication instructions and the supported MCP connection. Your assistant can also find a connection skill from Bloopbot’s public skill index. Reading these documents gives it information; connecting to your channel still needs your sign-in and permission choices.

1. Give the assistant a guide’s link, for example Build your first flow.
2. Ask it to fetch the page with Accept: text/markdown, or add .md to the guide’s address.
3. Ask it to use that guide to explain your next step. It receives the headings, instructions and links as text.

For example: “Read https://bloopbot.com/docs/flow-basics as Markdown, then help me plan a command that welcomes whoever I name.” The assistant can also read the guide index or all guides in one file.

If it still sees the browser page, use the address ending in .md. Reading a public guide gives the assistant instructions; connect it below when you want it to work with your channel.

Your assistant can read this channel’s published Social images, including their names and published revisions, and select one in an existing Post to step. Only published designs from your channel may be selected. It cannot create, edit or publish designs: make and review them in Social images yourself.

Before you start

• A Pro plan. Connecting an AI assistant comes with Pro. What your plan includes shows what your channel holds; if the assistant says it can't reach your channel, this is the first thing to check.
• An assistant that supports custom connectors. Some plans of some assistants only offer this on certain tiers; the assistant's own settings will show whether you can add one.
• Owner or editor on the channel. You connect as yourself, and choose which of your channels the assistant reaches. A moderator you have ticked on Team cannot connect an assistant; ask the owner or an editor.

Get help with your setup

Setup help can explain the tool you want to connect, using its own allowance. It does not grant an assistant access or unlock the AI capabilities of your plan. Keep keys, passwords and private setup links out of goal descriptions and help messages; use the normal connection and approval controls.

Connect it

Every assistant connects the same way: you give it Bloopbot's connector address, and it sends you to a Bloopbot sign-in and consent screen.

The address is:

https://bloopbot.com/api/mcp

1. In your assistant, add a custom connector (or MCP server) and paste the address above. Name it Bloopbot.
2. Choose Connect. Your browser opens Bloopbot's consent screen — sign in to Bloopbot first if it asks.
3. Pick the channel the assistant should reach, and check what it's allowed to do (see what it can and can't do).
4. Choose Allow. You're sent back to the assistant, and it can start working with the parts of your channel you allowed.

Where to add the connector, in the assistants most people use:

• Claude — Settings → Connectors → add a custom connector.
• ChatGPT — add it as a connector in ChatGPT's settings, where your plan allows custom connectors.
• Claude Code — run claude mcp add --transport http bloopbot https://bloopbot.com/api/mcp, then /mcp to sign in.

What it can and can't do

What the assistant may do is exactly what you leave ticked on the consent screen. Every permission it asks for starts ticked; untick any you don't want it to have:

• See your flows, packs, variables, collections and how they're wired — it can read every flow on the channel, including each step's full settings, the ordered members of your own packs, and your control panels with every button's fixed inputs. That includes anything you pasted into a step, such as a link in a Web request step, so only connect an assistant you trust with that. It can also see which text-to-speech voices your plan can use, so a Speak text step it builds names one you have; it can't add or change voices.
• Create and edit flows, packs, variable declarations and collections — every new flow it makes starts switched off. It can create several flows with the same name: Bloopbot gives each an available identifier when the assistant leaves it to Bloopbot. Editing a flow that's already on changes what it does straight away, the same as if you'd saved the change yourself, and it can move a flow to the trash. It can change or delete one of your own packs; deleting a pack leaves its flows and overlays alone. It can make, change and delete control panels, and add a Run button trigger to a flow so a panel button can start it. There's no permanent flow delete: anything it trashes comes back from the Trash. It can set up a collection and its catalogue of items (names, pictures from your media library, rarity and weight), but it can't give a viewer an item or take one away, can't see what a particular viewer owns and can't delete a collection. You do those on the Collections page, or a flow does.
• Run a flow as a test, without it going live — it can try a flow out and see what would have happened, without sending chat or showing anything on stream.
• Turn a flow on or off — lets the assistant switch flows on and off for you.
• Actually run a flow, for real — With it, the assistant can run a flow that starts with a Run button trigger, exactly as if you pressed Run in the editor: chat is sent, alerts show, points change.
• See your points store items and their settings — It can read an item's price, stock, limits, question and whether it is on sale.
• Create, edit and archive points store items — New items start off sale unless you ask for them to be available immediately. Editing an item already on sale takes effect for the next buyer. Archiving removes it from sale; past purchases remain in your history.
• See your overlays, themes and Studio drafts — It can read each overlay's and theme's published design, any unpublished Studio changes and the names, types, folders and tags of files in your media library. It can render a draft picture with sample content. Designs may include text and links you entered. It cannot see the private Browser Source key or URL.
• Create overlays and themes, edit Studio drafts and organise your media — It can create an overlay or a theme, edit part of an overlay draft or replace an overlay's or theme's full draft design, upload media files you give it, move, tag and rename files in your media library, and delete files nothing uses. A new overlay appears in Studio immediately, within your overlay limit; it reaches OBS only after you add its Browser Source there. A new theme waits in the draft. Draft changes do not reach OBS until they're published, by you in Studio or by the assistant with the permission below. Studio checks file type and storage limits, and refuses a draft save if someone changed it since the assistant last read it. It can also make a custom widget, put it on an overlay, change its code once for every overlay that shows it, restore an earlier version, make a separate copy, rename it, give it an icon and choose where it is listed in Studio's Add tab.
• Publish your Studio draft, so viewers see the changes — With it, the assistant can press Publish for you. That publishes your Studio draft, the same as the button in Studio: every unpublished overlay, theme, alert and wheel change, including ones you made yourself, or only the parts you choose, with anything they need. What it leaves out stays in the draft. Before it publishes, the assistant lists what will go live and waits for your go-ahead.
• See your public page, links, sections, gear and domain — It lets the assistant read the page's saved settings, including which pages are switched on.
• Edit your public page, links, sections, fonts and gear — The assistant can replace your full link and gear lists, change the section order, text, YouTube source and page-wide fonts, and switch Home, Giveaways, Store or Quotes on or off. Saves appear on your public page straight away when your plan includes the feature.
• Add, check and remove your public page domain — The assistant can start domain setup, check its status or disconnect it. You still add the DNS record with your domain provider. Custom domains come with Pro and may not be available on your channel yet.

Whatever it does is recorded under the assistant's name: the flow's version history and your Audit log say which changes came from it.

The assistant can choose which public command groups your Commands page lists. Moderator and broadcaster commands appear automatically only for signed-in viewers at those channel levels; the assistant cannot make them public by switching a group on. The Public page guide explains the page controls. If a save is refused because your plan does not include links or sections, check What your plan includes. The assistant's permission does not change your plan.

A worked example

With See, Create and edit and Run as a test allowed, ask: "Make a !hug command: when someone types !hug and a name, say that they give that person a big hug."

The assistant looks at your existing commands so it doesn't clash with one, drafts a flow with a Chat command trigger and a Send chat step, checks it, and runs it as a test. It then tells you the flow is saved and switched off. Open Flows, find it, look it over, and switch it on when you're happy.

Build a control panel

Allow See your flows and Create and edit flows when you connect. Then:

1. Ask: "Make a control panel called Match night for my Match day pack: a Home goal and an Away goal button for my Goal scored flow, and the home and away scores. Then put the panel in the pack."
2. The assistant reads what each flow asks for when it starts. A flow without a Run button trigger gets one first, and the assistant tells you about anything the flow reads that a button press leaves empty, such as the name of whoever typed a command.
3. It makes the panel with your buttons and tiles, fixing inputs where you said so, such as Team set to home on Home goal, and puts the panel in the pack.
4. Open Bot › Control panels and select Open on Match night to check it.

A pack's panel may only have buttons for flows in that pack, so the assistant adds the flows to the pack first. If you edit the same panel in the dashboard while the assistant works on it, it is told the panel changed and reads it again before saving. A channel holds up to 20 panels. The assistant can't press a panel's buttons; with Actually run a flow, for real allowed, it can run the button's flow instead. Control panels explains every tile.

Make a points store item

Allow See your points store items and their settings and Create, edit and archive points store items when you connect. Then:

1. Ask: "Add a Hydrate item to my points store for 50 points. Let people buy it once per stream, and keep it off sale until I review it."
2. Have the assistant show you the item's price, limit and sale status after it saves.
3. Open Loyalty and store under Viewers, choose the Store tab, review the item and switch it on when you're ready.

The new item appears in your store off sale. If the assistant says it needs store:write, reconnect it with the store edit permission ticked. Let viewers spend points in a store explains what happens when someone buys it.

Create an overlay

Allow See your overlays, themes and Studio drafts and Create overlays and themes, edit Studio drafts and organise your media when you connect. Then:

1. Ask: "Create an overlay called Chat corner with a Chat starting layer."
2. Ask the assistant to show the new overlay's name and starting layer. Open Studio to arrange the layer or add others.
3. When the design is ready, add the overlay to OBS using its Browser Source address from Studio. The assistant does not receive that private address.

The new overlay exists as soon as the assistant creates it. Later design edits stay in Studio's draft until you Publish. If it says you have reached your overlay limit, review your existing overlays in Studio before creating another.

Build a matching set

For a stream with several scenes, ask: "Show me Studio's overlay layouts. Make a matching gameplay overlay, Starting soon, Be right back and Ending screen, then show me a picture of each with sample content. Use the same colours and type across them."

1. Let the assistant list your existing overlays and the ready-made layouts. Your channel can have one screen for each scene role, so use an existing screen if you already have one.
2. Ask it to create the missing layouts. They follow your Active theme and appear in Overlays straight away. Ask it to make or edit a theme in the Studio draft if you want a new look, and preview each screen with that theme.
3. Check the pictures for legible text, room for gameplay and a consistent look. Ask for changes and another picture until the set works together. Open Studio to review the draft and Publish it. Make the new theme Active there if you want all the overlays to follow it.
4. Add each scene's Browser Source from Overlays to its matching OBS scene; set it to 1920 × 1080. The assistant does not receive those private addresses.

The pictures show sample content, so check the overlays against your own game and camera in OBS before going live. A scene that already exists keeps its Browser Source: ask the assistant to edit that screen's draft instead of creating a second one. Scene screens explains how they fit into OBS.

Design a look

Your assistant has Bloopbot's design guide to work from, so ask for a feeling, not a list of settings. It asks a few quick questions if you haven't said: three words for the vibe, your brand colours or logo, the games you play, and where your webcam sits. Then it picks one look, says it back to you in a sentence, builds a theme for it first and styles every screen from that theme. It checks each picture the way a viewer on a phone would see it, making sure the words read and the game and your face stay clear, before showing it to you.

1. Ask: "Design a cosy look for my channel. Warm and handmade, my colour is terracotta. I play Stardew Valley and my webcam is bottom right."
2. Look at the pictures it shows you and react in your own words: "bolder", "calmer", "bigger countdown", "less glow".
3. For moving backgrounds on your Starting soon, Be right back and Ending screens, give it a looping WebM video (up to 25 MB). It puts the video behind the whole screen and darkens it where the words sit. It doesn't put a video behind your gameplay overlay, where it would cover the game.

Design a matching set of overlays for my channel: gameplay, Starting soon, Be right back and Ending. The vibe is late-night, neon and a bit retro; my brand colour is #2DF5C6. Use the attached looping video behind the three break screens. Tell me the look you chose, then show me a picture of each and leave it all unpublished so I can review it.

The assistant can't make a video itself. If you don't have one, it suggests what to look for and uses a gradient in the meantime. A picture shows one still moment of a video, so watch the loop in Studio before you go live.

Edit an overlay draft

Allow See your overlays, themes and Studio drafts and Create overlays and themes, edit Studio drafts and organise your media when you connect. Then:

1. Ask: "Show me the layer types Studio can add, then show me my Starting soon overlay and change its headline to 'Stream starts in five minutes' in the Studio draft."
2. Ask it to show a picture of the draft over sample stream content. If text is cramped, a layer covers gameplay, or the colours are hard to read, ask it to adjust the draft and show another picture.
3. Open Studio, select Starting soon, review the draft, and choose Publish when it looks right.

Ask for “a preview on black” to check the overlay on its own, or “preview it over this gameplay screenshot” and give the assistant a direct public HTTPS image link. PNG, JPEG, GIF and WebP images up to 5 MB work; a private link, a redirect or a file that cannot load is refused. The picture is centred and cropped to fill the preview player. This background is only for the picture and does not become a layer in your overlay. With no background link, previews use black.

The picture uses your draft layout and theme with made-up chat, alerts and other sample content. It is not a capture of your live stream. The assistant reads the latest Studio draft before saving. If Studio says the draft changed, ask it to read the overlay again and apply your change to the newest version. Arrange your overlay walks through reviewing and publishing.

For a new picture, sound or video, give the file to your assistant and ask it to upload the file to your media library before adding it to the draft. PNG, JPEG, GIF, WebP, MP3, OGG, WAV and WebM files work, within the same size and storage limits as Studio: a picture or a sound up to 5 MB, a WebM video up to 25 MB, and your channel's media storage. A file over its limit is refused and nothing is saved.

How quickly the upload goes depends on your assistant:

• An assistant that can run commands on your computer, such as Claude Code or Codex, asks Bloopbot for a one-time upload link and sends the file to it directly. That takes seconds, even for a 25 MB video. The first time, your assistant may ask you to allow the curl command it uses to send the file. Each link works once, for 15 minutes.
• An assistant that can only chat has to spell the whole file out as text. That is slow, a few minutes even for a small picture, and only works for files under 3 MB.

If your assistant cannot send a file to Bloopbot, or a large file is taking too long, upload it in Studio's Media tab first, then ask the assistant to use that existing file.

Publish from your assistant

Allow Publish your Studio draft, so viewers see the changes as well as the two overlay permissions when you connect. Then, once a draft looks right in the pictures:

1. Ask: "Publish my overlay changes."
2. The assistant lists every change waiting in your Studio draft, for example "Starting soon: changed overlay settings" or "added theme Night show", and asks which to publish.
3. Say "all of them" or name the ones you want. The assistant publishes, and your Browser Sources in OBS update within a few seconds, just as when you press Publish in Studio.

You can publish just some of it. Say "Publish only Starting soon" and the other changes stay in your draft, as when you untick them in Studio's Publish your overlay review. If what you pick needs an alert design or theme that isn't live yet, that goes too, and so can another overlay (when you renamed an alert design that several overlays show, they go live together), and the assistant tells you so before it publishes. If you or an editor changed the draft since the assistant last looked, it tells you what's new and asks again. If a published change turns out wrong, open Studio, choose History, restore the version from before it into your draft and publish again (Arrange your overlay explains History).

Without this permission, the assistant tells you the draft is ready and you publish it in Studio yourself.

Keep your media library tidy

With the same two overlay permissions, your assistant can file what it uploads into a folder and label it with tags. Studio's Media tab and every media picker let you browse by those folders and tags, and the Media page in the sidebar is where you manage them. Ask for it in your own words: "Upload this as a sub alert picture into a folder called Alerts/Subs, and tag it cute." Folders can be nested up to three levels, a folder name is up to 48 characters, a file can carry up to 20 tags, and the assistant creates a folder that does not exist yet. If it cannot make the folder (for instance you have reached the folder limit), the file still goes into your library at the top level and the assistant tells you.

It can also tidy files you already have: "Move my four sub pictures into Alerts/Subs and tag them cute", "Rename that file to Sub chime", or "Show me everything tagged cute." It looks files up by folder, tag or part of a name. It can also read how your library is organised, every folder with how many files and subfolders it holds and every tag with how many files carry it, so "What folders do I have?" or "Which tags do I use most?" gets a real answer, and it can reuse a folder or tag you already have instead of making a near-duplicate. Seeing the folders and tags needs only the See your overlays, themes and Studio drafts permission. Moving, tagging and renaming a file never breaks an overlay or theme that already uses it. A new file name can use letters, digits, spaces and the characters _ . ( ) -, up to 80 characters; the assistant is told when a name needs changing. If you upload a picture that is already in your library, the assistant tells you where the existing copy lives instead of adding another; the copy stays put and any tags you asked for are added to it. Files you install from the marketplace appear in a folder called Marketplace, inside a folder named after the listing.

It can delete files you no longer need: "Delete the three old sub pictures in Alerts/Subs." Deleting is permanent, so the assistant names the exact files and waits for your go-ahead before it deletes anything. A file that something still uses is kept, even if you ask. That includes an overlay, a theme, an alert design, a giveaway, a points store item or a flow, published or waiting in your unpublished Studio changes. The assistant tells you what uses it, so you can swap the file out there first. It deletes up to 200 files at a time, and the rest still go if some are kept.

Your assistant cannot delete folders, and it cannot publish anything to the marketplace. Deleting a folder can remove files something still uses, so you do it yourself on the Media page, where you confirm by typing the folder's name. Publishing needs you to confirm you have the rights to what you share, so that stays with you too.

Create a theme

Allow the two overlay permissions when you connect. Then:

1. Ask: "Make a theme called Night show from my current theme. Use a deep navy panel and warm gold accent."
2. Ask the assistant to show the colours, type and any alert designs it changed, then show a picture of one of your overlays in the new theme. Ask it to refine the look and preview again as needed.
3. Open any overlay in Studio, choose Theme, select Night show and review it on the canvas. Choose the check icon (Make Active) if every overlay should follow it, or use it on one overlay. Press Publish when it looks right.

The assistant can also start with Studio, Capsule, Scoreboard or Minimal. A new theme stays in your draft and does not change OBS until you publish. If your plan's theme limit is reached, Studio asks you to replace or remove a theme before creating another. Style every overlay with a theme explains themes and how they affect overlays.

Add a frame to your panels

Allow the two overlay permissions when you connect. A frame is a picture drawn as a border round a panel, a chat line or an alert card (Put a frame around panels, chat lines and cards). Then:

1. Attach a PNG or WebP frame picture with a see-through middle, and ask: "Upload this as a frame and put it round the panels in my Night show theme. Its corners are 32 pixels, so cut it at 32 and draw it 16 pixels thick."
2. The assistant saves the frame in your draft, then shows a picture of one of your overlays in that theme and checks the corners. If they look squashed or the frame covers your text, it changes the corner size, the thickness or how the sides fill, and shows another picture. You can ask for the same by hand.
3. To frame just one layer, name it: "Give the Follow alert layer its own thicker frame." The assistant sets that layer’s own frame and leaves the theme’s as it was. To keep the theme’s frame off one layer, or one part such as a chat line, say so: it sets that layer’s or part’s frame to None, which clears it completely.
4. Open Studio, look the draft over, and press Publish when it looks right.

Upload the attached PNG as a frame and use it as the panel frame of my Night show theme, with 32 pixel corners and a frame width of 16. Then show me a picture of my Starting soon overlay in that theme. Leave everything unpublished so I can review it in Studio.

What the assistant knows about frames, and what you can rely on:

• A frame’s Frame width replaces the box’s own border width, including a Border set on a part under Parts. Studio, Capsule and Scoreboard give alert cards, and chat lines in the Bubbles layout, a 2-pixel border (Capsule’s chat lines have one in every layout), so a frame’s width takes its place there. Minimal draws none.
• None on a layer or a part clears a frame completely: no picture, and no thick edge left behind.
• A chat line frame works in every chat layout.
• A Poll card, the End credits panel, an Image layer and a Box or Circle shape take the panel frame. A Divider and a Minigames layer take none, so the assistant will not promise one there, and a frame set on a layer that draws none is refused.
• A theme the assistant copies keeps its frames.
• A picture used as a frame must be an image; a sound or a video is refused. When Bloopbot refuses a save, it says which field was at fault, for example a layer’s frame picture, so the assistant can read it and fix it.

If your assistant cannot send a file to Bloopbot, upload the picture in Studio’s Media tab first and ask it to use that file. The frame waits in your draft like any other change until you publish.

Remove it

Open Settings › Connected apps in your channel's sidebar and select the bin icon (Revoke) next to the assistant. It's signed out straight away and can't reach your channel again until you connect it again. See and remove connected apps covers the page.

Troubleshooting

• "AI assistant connection is not included in this channel's plan" — connecting an AI assistant comes with Pro. Check What your plan includes.
• "Missing scope" when it tries to do something — that permission wasn't ticked when you connected. Revoke it on Connected apps, connect it again, and tick the permission on the consent screen.
• It says a flow is paused when it tries to run it — the flow is switched off, or it has no Run button trigger. Only a switched-on flow that starts with Run button can be run.
• "Busy" or "too many runs" — the flow is already running, or it has been run a lot in a short time. Wait a moment and try again.
• A social post step it made says the account is not connected, or needs reconnecting — the assistant can't connect accounts. Open Settings › Connections, connect or reconnect that network, and run the flow again. A message that posting to a network isn't available yet means the network isn't offered on your channel yet, not that the step is wrong.
• A Discord step it made says to choose a server and channel — the assistant can't see your Discord servers, so it leaves them empty. Open the flow, choose the server and channel in the Post to Discord step, and save.
• A save is refused because the flow changed — someone saved the same flow in the meantime. The assistant is given the latest version so it can redo its change on top.
• An upload takes minutes, or a file of 3 MB or more won't upload — your assistant is spelling the file out as text. An assistant that can run commands on your computer, such as Claude Code, uses a one-time upload link instead and takes seconds; see Edit an overlay draft. Or upload the file in Studio's Media tab and ask the assistant to use it.
• A custom widget takes minutes to save — for a small edit, ask the assistant to patch the widget with only the changed snippet, rather than send its whole code again. It edits the widget once, for every overlay that shows it. See Work with your widgets. A graphic that is not a widget can use a source link instead: see Ask for a custom graphic.
• "This upload link is unknown, already used or expired" — each upload link works once, for 15 minutes. Ask the assistant to upload the file again; it gets a new link.

Ask for a custom graphic

An assistant can author HTML, CSS and TypeScript or JavaScript in a Custom graphic layer, with the bundled GSAP or PixiJS libraries. Give it the events, named flow messages, variables and editable settings you need; ask it to create or reuse a delivery flow for every selected alert and message; ask it to discover the graphics contract, save source to the Studio draft, then render a simulated event at a chosen timestamp. To check an animation, ask for a frame strip: up to twelve timestamps rendered as one image each, such as the entrance, the hold and the exit. Ask it to declare the values each flow message carries, so the flow editor can fill in and check the Send to overlay rows. Ask it to add examples and a demo, such as “a small raid, then a huge one two seconds later”, so whoever adds your graphic can press Play example; its previews then play that demo. Review the expanded code-and-preview workspace before Publish. See Author a custom graphic for a prompt and the complete workflow. A TypeScript mistake never blocks its save; the assistant is told the line to fix.

For later edits, the assistant can change just the affected source snippet or setting. It keeps the rest of your graphic and saves to the same Studio draft.

1. Connect with See your overlays, themes and Studio drafts and Create overlays and themes, edit Studio drafts and organise your media permissions and ask the assistant to read your current graphic.
2. Give it a focused change, for example: “Change the raid card accent from red to green. Use patch_overlay_draft with only the changed snippet; keep the rest of the graphic.”
3. Ask it to preview the changed raid card, then review the result in Studio before Publish.

A graphic you installed from the marketplace may be sealed: its creator kept the code private, so the assistant can't read or change it. It can still read the graphic and change its settings, messages, variables and sound volume, and it will tell you if you ask for new code. See Sealed graphics.

A small edit no longer needs the assistant to send all the unchanged HTML, CSS and JavaScript again. The first version or a complete rewrite still needs the new source. If Studio changed in the meantime, the assistant must read the latest draft and reconcile its edit. If the same snippet appears more than once, it must include enough surrounding text to identify the intended change. A refused patch saves nothing; OBS keeps the published version until you publish the draft.

This is for a graphic that is not one of your widgets; a widget's code is patched instead. A big graphic saves fastest from files. An assistant that can run commands on your computer, such as Claude Code, keeps the graphic's HTML, CSS and JavaScript as files, asks Bloopbot for a source link once and sends each changed file in a second or two, instead of writing the whole code out, which can take minutes. You can ask for it directly: “Keep the raid card's code in files and send them with a source link.” Each file lands in the same Studio draft through the same checks as any other save. A link lasts 15 minutes and saves up to three times; if you edit the graphic in Studio in the meantime, the link stops working and the assistant reads your latest draft and asks for a new one, so your change is never overwritten. Nothing reaches OBS until you Publish.

Work with your widgets

Your widgets are kept once and shown on as many overlays as you like. With See your overlays, themes and Studio drafts an assistant can list them, see which overlays show each one and read its code. With Create overlays and themes, edit Studio drafts and organise your media it can also:

• make a widget and put it on an overlay, at a position you ask for or top left by default, for you to adjust in Studio;
• change a widget's code once, for every overlay that shows it, in your draft;
• bring back a version you published before, or delete a widget and its layers in your draft;
• give one layer its own copy, rename a widget, set its icon, and choose where Studio's Add tab lists it.

For example: "Make my raid card widget's accent green, and list it under Raid alert." Its code changes wait in your draft until you press Publish, or the assistant publishes with your go-ahead; a name, an icon and Listed under apply at once. It can't read or change a sealed widget's code. A widget's code is changed by patching the widget, not with a source link: a source link works only for a graphic that is not a widget.