Complete plain-text overview — what it is, what it does, what hardware it supports, and how it compares.
Lurk OS is a Windows desktop application for Rumble livestreamers. It pairs a local-first AI co-host named GLITCH (powered by Ollama on your own PC) with a full engagement toolkit: chat reader, custom commands, timed messages, a viewer economy with games, an event-driven soundboard, sponsor/affiliate rotation, and an AI-generated mini-podcast generator for stream breaks (BRB Studio).
Everything that needs to stay private — your chat history, your viewer profiles, your AI conversations, your embeddings — lives in a single folder on your PC called shared_data/. Nothing about your stream is sent to a third-party cloud you don't control. Internet is used only for the few things that genuinely need it (Google Cloud Speech for mic input, Rumble's chat API, DuckDuckGo and NOAA for the BRB news/weather feed, and a one-time license-key verification on first launch).
Lurk OS is opt-in two-PC. On a single beefy PC, run it end-to-end. On a streaming rig + AI rig, run PC1 as "the brain" (Ollama, bot server, shared data) and PC2 as "the station" (a thin UI that proxies everything back to PC1). The split is a config switch, not a separate install.
Every panel, one line each.
!ai / !glitch <q>). Short, punchy replies (~200 chars). Knows the asker's history (returning viewer? mod? donor?) and adjusts tone accordingly.@glitch without asking anything.Every chat message becomes a vector embedding (default model: nomic-embed-text via Ollama). Past conversations are searchable. When GLITCH replies, it pulls in the most relevant prior context, so it doesn't forget who you and your regulars are between streams.
Generates a fresh mini-podcast every stream break. Two AI voices (narrator + guest character). Pulls live data: space weather from NOAA, gaming news via DuckDuckGo. Plays through OBS or local speakers.
The "pushiness" knob (very_subtle / subtle / decent / pushy / very_pushy) decides how aggressively the AI weaves your sponsor/affiliate mentions into !ai replies. Off if you want a clean chat.
Up to 30 messages of history are passed to the model each call. The AI can ask for follow-ups itself (the "agent loop") — useful for multi-step answers like "look up X then summarize."
Lurk OS does not become a doorstop when Ollama is down. Every non-AI panel still works:
Manual click-to-play pads, event-triggered clips (raid / follow / sub / donation / first_chat), keyword bindings ("if chat contains X, play Y"), per-clip cooldowns, global cooldown, master volume. Route per clip: local winsound or OBS media source.
Dual currency: Stash Credits (low tier) + Cartel Coins (high tier). Commands: !points, !top, !shop, !duel, !heist, !roll, !gift, !convert, !loot, !stash, !boss, !unlurk. Configurable drop rates, cooldowns, role gates. Expandable gear database for loadouts.
User-defined !whatever with cooldowns and role gates (anyone / regular / mod / streamer). Random response picker.
Auto-posts on a fixed interval. Skip-if-chat-dead threshold so the bot doesn't talk to an empty room. Affiliates can ride in the rotation.
Managed URL list with discount codes and short blurbs. Used by the timed-message rotation and the AI prompt; the rotation itself does NOT need AI.
Master + 6 lanes (chat TTS, GLITCH reply, bot, BRB narrator, BRB assistant, legacy pyttsx3). Per-lane mute / volume saved per PC.
Each stream gets auto-saved as a Project containing one searchable Chat ([HH:MM:SS] username: text). Persists on stream end. Searchable across past streams.
Scene switching, source toggling, BRB playback. Configured in Settings; can run on PC1 or PC2.
Mouse Button 5 → mic capture → STT → routes to AI (PC1) or remote PC1 from PC2.
If Ollama isn't reachable on launch, the Status bar shows a red "AI: offline" pill that clicks through to the Status page where you can repair the daemon.
Two roles, one codebase.
localhost:11434).bot_server on port 5051 (Flask) so PC2 can read / write data.shared_data/ — the single source of truth.app.py, but role=pc2 in local_config.json.bot_server. There is no "local edits drift away from PC1" — edits on PC2 land at PC1.7778 so PC1's TTS can be played out PC2's speakers (the actual streaming PC).Lurk OS auto-detects your GPU at install time (install.bat → setup/hardware.py) and pip-installs only the matching monitoring library. The Status page reflects the result.
If install.bat misdetects your hardware (or you swap GPUs later), open the setup wizard again and click "Retry hardware install" on the Hardware step.
rumble_poller) is also available if SSE is ever blocked.4455). Scene switching, source toggling, media playback for BRB clips.localhost:11434. Auto-starts on app launch if not already running. Default model: llama3.2:3b (configurable).INSTALL_PIPER.bat. Without Piper, Windows SAPI (pyttsx3) is the fallback.These are honest comparisons, not marketing. Lurk OS is good at some things and explicitly not trying to be others. If a product on this list is the right tool for your job, use it.
Server-side. Timers, simple !commands, basic auto-mod. No AI. No memory of past viewers. Read-only from your side — you can't extend it.
Everything Rumble's bot does, plus:
Reads chat via SSE direct from Rumble (real-time). Sends through YOUR logged-in account, so replies look like the streamer — not a third-party bot agent that viewers have to trust separately.
Visual node-editor automation. Heavy on Twitch hooks (Twitch is its native platform). Excellent for complex if-this-then-that flows. No bundled AI. No semantic memory. No TTS-with-memory.
Rumble-first. AI is a first-class citizen, not a plugin you have to wire up. Less flexible than Streamer.bot's node graph; more out-of-the-box for streaming + AI.
Lurk OS BRIDGES to Streamer.bot via the bundled WebSocket relay (VGC_BOT/streamerbot_relay.py) if you want both: Lurk OS for AI / BRB / economy, Streamer.bot for visual automation.
Cloud-hosted bot + an OBS-derived encoder UI. Twitch + YouTube focused. Closed source. Subscriptions for advanced features. Your chat data lives on their servers.
Fully local. No subscription. No cloud dependency for AI or chat storage. Your chat data stays in shared_data/chats/ on YOUR machine.
No streaming encoder built in — you bring OBS. (We think encoding is OBS's job, not the bot's.)
Free, open-source bot. Strong command / games support. Twitch / YouTube / Trovo native — not Rumble. No AI. No semantic memory.
Similar command + games surface (we ship a 12-command built-in suite plus a dual-currency economy with duels, heists, rolls, gifts, gear), AND adds:
Rumble is our native platform; we read chat via SSE directly. Mix It Up doesn't currently support Rumble.
OBS Studio + advanced-scene-switcher + browser-source overlays + custom Lua / Python scripts + a separate chat bot tool + a separate sound-effect tool + a separate alert tool. Maximum flexibility, maximum maintenance.
Replaces the "plus" — the 10+ plugins, the bot, the AI overlay, the chat reader, the soundboard, the BRB system — with one Python program you can read. OBS still does the streaming; Lurk OS does the brain.
If you love wiring plugins together, the DIY route stays flexible. If you want it to work end-to-end out of the box, this is the tradeoff.
Local-first by default. What stays on your PC:
shared_data/chats/)shared_data/memory_index.jsonl)shared_data/bot_data/)shared_data/soundboard/)channel_config.json)stream_config.json so another Windows user can't decrypt it from a copy of the file)You can see exactly when the network is touched by watching the daily log at logs/lurk_os_<YYYY-MM-DD>.log.
Per-user personal license. Non-transferable. See LICENSE.txt for full terms. Bundled third-party software (Piper, customtkinter, requests, flask, etc.) is licensed under their own terms — see THIRD_PARTY_LICENSES.txt for the full list and SPDX identifiers.
Support, feature requests, bug reports: contact VGC Media via the channel where you bought your license. Critical bugs that block a stream get priority; cosmetic gripes get a fix in the next update.
logs/lurk_os_<YYYY-MM-DD>.log for the actual error.If you're going to ship Lurk OS to another PC (e.g. PC2 in a two-PC setup), copy the full install folder plus shared_data/, then run install.bat on the new machine. The vendor-aware installer will detect the new GPU and install the right monitoring SDK automatically.
Lurk OS is available now on Gumroad. One-time price, no subscription, your data stays on your machine.
Get Lurk OS on Gumroad →The same doc ships with every Lurk OS install. Grab it for offline reference or sharing.
Download ABOUT_LURK_OS.txt →