RaidBridge

RaidBridge turns an incoming Twitch raid into a short, streamer-approved shared onboarding ritual instead of a burst of generic “welcome raiders” messages.

The problem

Raids are one of Twitch’s most community-native moments, but the transition is usually abrupt. A new group arrives with its own context, the host is mid-stream, and both communities have only seconds to understand what is happening.

What RaidBridge does

When Twitch EventSub reports an incoming raid, RaidBridge creates a private proposal for the receiving streamer. Nothing appears publicly until the streamer approves it.

Once approved, an OBS browser-source overlay runs a bounded 90-second sequence:

1. Arrival — who raided and how many viewers arrived.
2. Context — concise, host-approved context about the receiving stream.
3. Bridge — a lightweight shared prompt chosen from deterministic templates using available Twitch context.
4. Welcome — a clean completion card that closes the transition and returns focus to the stream.

The streamer can approve, skip, or abort instantly.

Why it is different

RaidBridge is not a poll, prediction game, generic chatbot, or chaos engine. It focuses on one Twitch-native moment: helping two communities successfully merge when a raid happens.

Current hackathon research showed a crowded field around polls, chat-controlled games, dares, story voting, and general-purpose overlays. RaidBridge deliberately stays small and specific: make the raid transition itself better.

Trust and reliability boundaries

• Raw untrusted chat text is never automatically rendered to the OBS overlay.
• The receiving streamer is the final authority over what appears publicly.
• Repeated EventSub deliveries are processed idempotently.
• Malformed or stale events fail closed.
• Rehearsal data is explicitly labeled synthetic and travels through the same state machine as live raid events.
• Failed live Twitch calls never silently fall back to simulated evidence.
• Twitch credentials remain server-side and are never committed to source control.

Twitch + Codex

The project is being built during the hackathon in a persistent OpenAI Codex session. Codex is implementing the TypeScript raid state machine, EventSub WebSocket lifecycle, Twitch OAuth/Helix integration, streamer control deck, OBS overlay, rehearsal path, tests, and documentation.

Primary Codex session ID: 01a18985-46db-7cd3-9564-24c9d10ec4ad

Live Twitch validation, repository URL, final video, and exact testing evidence will be added only after they are genuinely verified.

Built With

• node.js
• oauth2
• obs-browser-source
• openai-codex
• twitch
• twitch-eventsub
• typescript
• websocket