VibeStreaming supports YouTube Live loops without OBS or manual restarts

• youraipulse's June 3 demo framed VibeStreaming as a way to turn one video file into a 24/7 YouTube stream without keeping OBS open all day.
• In youraipulse's follow-up test, the project was already running a small stream from local video through a server into YouTube Live, with no manual restarts since June 3.
• The GitHub repo says the app is a local Windows web app that creates a YouTube Live broadcast, loops the video indefinitely, and auto-reconnects ffmpeg after temporary RTMP failures.
• According to youraipulse's link post and the repo's README, the 24/7 promise still depends on an always-on PC or a private Windows VPS, because the stream stops if the host machine sleeps, shuts down, or loses internet.

You can watch the live test, browse the repo, and the README gets more specific than the tweets do: the app runs at 127.0.0.1:8765, stores OAuth tokens and uploads locally, and already exposes disabled Twitch and X/Twitter slots marked SOON.

The core pitch is narrow and useful. VibeStreaming takes a single video file, opens a YouTube Live broadcast, and keeps looping that file without an OBS session sitting open in the foreground.

AmirMushich's quick-start post pushed the same angle from the creator side, pitching YouTube streaming "in seconds." The repo backs that up with a short flow: connect Google OAuth, pick a channel, choose a video, set metadata, click >run, and get a watch link back.

The README says the app is Windows-first and launches through start.bat, which checks for Python 3.10+, installs ffmpeg if needed, creates a local virtual environment, and opens the interface at http://127.0.0.1:8765.

That same README is also where the cleanest caveat lives: the stream only exists while the machine, app, and ffmpeg process stay running. A local PC is fine for testing, but the repo says continuous streaming means either preventing sleep on your own machine or moving the whole stack to a Windows server or VPS.

One extra detail in the repo did not make it into the tweets. The current alpha is YouTube-only, but the UI already reserves space for Twitch and X/Twitter, both labeled SOON, and the README says the internal RTMP setup already supports multiple outputs.

The same section is blunt about where the sensitive bits live. OAuth files, channel tokens, videos, thumbnails, logs, and run history stay in the local .\\data folder, and the repo tells anyone using a VPS not to expose port 8765 publicly or leak token files from that directory.