From the audience side, a ReactivVibeAI live show looks deceptively simple: a host on a stream, a track plays, a queue moves, the chat reacts. From the host's side, it is a stack of half a dozen coordinated systems, each with its own failure mode. We've spent the last several months tightening this stack, and the picture below is what an actual live session looks like for a host running a one-hour show. None of this is hypothetical; this is the literal screen layout of a host running a typical Tuesday night.
The browser windows
A typical host has at least four browser windows open during a show. The first is the main host studio at /live/<their-slug>, which is where the queue lives and where the host controls playback. The second is the stream destination — usually TikTok Live, sometimes YouTube — open in its native interface so the host can read chat without it being filtered through an overlay. The third and fourth are popout windows for the queue and the now-playing display, rendered transparently so they can be dropped straight into OBS as browser sources.
Hosts who run higher-production shows add a fifth and sixth: the ranking board popout (so the leaderboard is on stream during voting moments) and the prize wheel popout (used at the end of the session). Each of these is its own URL with its own state, designed specifically so that nothing on the host's main monitor can leak into the stream layout. We learned this the hard way after a host accidentally captured an entire admin panel into a stream during week two.
The OBS scene
OBS is where everything composites. A typical scene has the camera at the top, the now-playing card in one corner, the queue in another, and a chat overlay along one side. Each card is one of our popout URLs loaded as a browser source, with transparency enabled. Because the popouts know they're popouts (the URL path tells them so), they render with no background, no navbar, and no footer — just the content card.
The single most common host mistake we still see is forgetting to set the browser source dimensions to match the popout's actual layout. Our popouts are designed for a fixed pixel range and don't reflow gracefully if you stretch them past their breakpoint. We document the recommended dimensions in the host onboarding flow, but anyone who has worked with OBS will not be surprised that this is the number-one support question we get from new hosts.
The hype bar and the TikTok sync
The hype bar is the bar at the bottom of every audience-facing surface during a live session, showing how much energy the current track is generating. It moves in response to two things: in-platform Spark spends, and — when configured — TikTok-side gifts and likes being mirrored over.
That second part is the one that produced our most-debugged feature of the year. The TikTok sync is a single global "lease" that the platform issues to one host at a time. The reasoning is mechanical: the sync polls the TikTok side, and only one host can be the recipient of those polled events at any moment. If two hosts are both live and both have the sync enabled, the lease goes to whoever claimed it first, and the other host's hype bar will appear to "not update" — which is technically correct but confusing in the moment.
We've now made this visible. Every host's panel shows whether they currently hold the sync lease, when the last heartbeat arrived, and the TikTok username configured. We've also added a manual on/off toggle so a host can voluntarily release the lease when they're done for the night, instead of waiting for the timeout to expire. This is the kind of feature that exists entirely because we kept getting the same support message: "Why is my hype bar broken when bone man is live?"
The submission queue
Submissions arrive into a queue that the host can re-order, skip, play, or send to the back of the line. Boosted submissions appear with a visual indicator and slot in ahead of unboosted ones, respecting the order in which they were boosted. Skip-the-line submissions go to the front, full stop, and the audience sees a dedicated overlay event when one comes through.
The queue is also where most of the host's judgment lives. We do not have any algorithm choosing what plays next. The host makes the call, with the queue, the boost amount, the audience reaction, and the show's pacing all on the same screen. This is intentional. The whole reason this format exists is that a real human curator makes more interesting decisions than a recommendation engine, and the audience can feel the difference.
The end of show
We've watched a lot of hosts struggle to land an ending well. The pattern that consistently works: announce a wind-down five minutes before the actual end, run the prize wheel if the show has one, thank the top three contributors by name from the leaderboard, and cut. The leaderboard popout is the unsung hero here — having the right names visible on stream at the moment of thanks closes the feedback loop for the audience and reliably converts to repeat attendance the following week.
After the cut, the host has one last thing to do: end the session in the studio panel, which finalises the leaderboard, locks the post-show recap, and triggers any boost rebates back to the creators whose tracks were played. We forgot to build this for the first month and recoiled when we realised hosts had been manually keeping notes. It's a button now.
What still goes wrong
Honestly: audio levels. AI-generated tracks vary wildly in mastered loudness, and a host running the queue can get blown out by a track that arrives ten dB hotter than the one before. We're looking at per-track normalisation in the queue player, but it's not shipping yet. For now, the working hosts solve this with a hardware compressor in front of OBS or a software equivalent on the playback channel. It's a real friction point and we know it.
Beyond that, the platform side is now stable enough that the most common cause of a "broken show" is the host's network or capture software, which is the normal failure mode of any live production. That's a reasonable place to be, and it's where we wanted to land: the platform fades into the background, and the host's job is the show, not the technology.