HK//HACKERSHACKATHONS · KAGGLE · FOR BEGINNERS中文
HACKERS / Hackathons

Codex x TwitchCon Hackathon 2026: a beginner guide to building for Twitch chat

OpenAI and Twitch pay $25,000 for interactive Twitch projects built with Codex, and the top five are shown on the Codex Booth stage at TwitchCon San Diego on Nov 15. Entries close Nov 2, 2026 at 2:00 pm PT, so you have about a week. Most ideas here run through chat, so before writing anything we recorded five minutes of real Twitch chat on Oct 26. The busiest channel sent 2,230 messages from 957 people and peaked at 37 messages in a single second. A bot that is not a moderator may send one message per second. Only 2% of messages were bare answers like "1", "A" or "yes", and half the chatters wrote exactly once. Design for that crowd: count votes instead of replying to each one, keep commands short, and make the first message count.

This competition has ended. The guide is kept for reference; the next edition may change rules, judging and dates, so check the official page first.

DEADLINEClosed
PRIZE—
Official page ↗

Brainstorm word cloud

Not enough text on the public pages yet to mine terms. The cloud appears once the brief or the project gallery has more to read.

Key facts

What you build
An interactive experience for Twitch streamers and their community, built with OpenAI Codex during the submission period. It must connect to Twitch, for example through chat, a stream overlay, the Twitch API, EventSub or an Extension, and it must run as shown in your video ↗
Prizes
1st $10,000, 2nd $6,000, 3rd $4,000 and two runner-ups at $2,500, all with stage time at TwitchCon. Travel to TwitchCon is at your own cost, and not attending does not forfeit the cash ↗
What to submit
A GitHub, GitLab or Bitbucket repo with all code and run instructions (a private repo must be on GitHub or GitLab and shared with testing@devpost.com), a text description that says how you used Codex, the Codex session ID of the thread where most of the build happened (type /status in Codex), and a public YouTube video under 3 minutes ↗
The video needs two kinds of footage
The rules ask for footage of the project working on Twitch and footage of how it was built with Codex. Judges do not have to watch past 3 minutes, and they may judge from the video and text alone without testing your build ↗
Who can enter
Individuals 18 or older (or the age of majority where they live) and teams. Organizations are excluded, as are residents of Brazil, Quebec, Russia, Crimea, Cuba, Iran, North Korea and other comprehensively sanctioned places. Several entries per person are allowed if each is substantially different ↗
How busy chat really gets (our measurement)
We read 5 minutes of public chat on Oct 26, 2026 from 05:57 UTC with an anonymous IRC connection. caseoh_ sent 2,230 messages from 957 chatters, about 7.4 a second on average and 37 in the busiest second, with a median length of 10 characters. 491 of those chatters wrote only once. summit1g peaked at 11 a second, and on amouranth 42% of messages were emotes only ↗
How fast a bot may talk
A bot that is not the broadcaster, a moderator or a VIP may send 20 messages per 30 seconds and 1 message per second per channel. As broadcaster, moderator or VIP it gets 100 per 30 seconds. Going over makes Twitch ignore the bot's messages for 1 hour. Identical messages within 30 seconds are rejected as msg_duplicate ↗
Verified bots are not an option this week
Verified bots may send 7,500 messages per 30 seconds, but Twitch says reviews for chatbot verification are temporarily paused, so plan around the normal limits ↗
Joining channels
One account can be in 100 chat rooms at once (since May 15, 2024) and may try 20 joins per 10 seconds. In rooms with more than 1,000 users your bot gets no JOIN or PART messages, so you cannot count viewers that way ↗
What Skill Rank shows
Of the 1,024 agent skills tracked on PocketPlay Skill Rank on Oct 26, 2026, none mention Twitch, EventSub or livestreaming. There is no ready-made skill in that catalog to lean on, so budget time for reading the Twitch docs ↗

Idea angles

Our scoping ideas for beginners, built from the official directions and our chat measurement. They are not official briefs.

Crowd vote that counts instead of replying (Audience participation)

Read every message, tally answers in 10-second windows and show the result on an overlay. One bot message per window stays far under the 1-per-second limit even when chat runs at 37 a second. Prompt clearly: unprompted, only 2% of messages looked like votes.

Raid welcome kit (Streamer collaboration)

Listen for raid events (USERNOTICE msg-id raid on IRC, or the matching EventSub event) and give the raiding community a short shared goal on screen. The hackathon forum already runs a raid swap, which gives you real raid footage for the video.

First-message onboarding (Audience participation)

Half the chatters on caseoh_ wrote only once. Turn a viewer's first message into something visible, such as their name joining a map or a team, using the viewermilestone notice, which Twitch documents for milestones such as a viewer chatting for the first time.

Emote-only game input (Content enhancement)

On amouranth 42% of messages were emotes only. A game that reads emotes as moves still works when a room switches on emote-only mode, which blocks plain text.

Mode-aware overlay (Design)

Rooms announce followers-only, slow, emote-only and r9k modes in ROOMSTATE. Show viewers which input still works under the current mode, so nobody spams a command the room is blocking.

Judging criteria

Rules: Stage One is pass/fail on whether the project fits the theme and uses Codex. Projects that pass are scored on four equally weighted criteria, and the five highest become finalists. Ties go to the higher Innovation/Idea score, then the next criterion. The rules allow expert panels, peer review and automated AI analysis. source ↗

Innovation/Idea25%

How new the concept is compared with existing ideas. The organizers list Twitch Plays games, polls and dice rollers as starting points, not templates, so a straight rebuild of those starts behind.

Potential Impact25%

How useful or entertaining it is for streamers and their communities. Show a real streamer, or a real raid, using it rather than an empty test channel.

Technological implementation25%

How well it is built and how well it uses Codex. Your session ID and the Codex footage in the video are the evidence here.

Design25%

Whether it is easy to use and fun to watch. Viewers type about 10 characters per message, so a one-word command reads better on stream than a form.

Starter stack

  • Example Chatbot (Twitch docs) The guide the organizers point to. A Node.js bot that listens on the EventSub WebSocket wss://eventsub.wss.twitch.tv/ws, needs the scopes user:bot, user:read:chat and user:write:chat, and replies through POST https://api.twitch.tv/helix/chat/messages. It answers HeyGuys with VoHiYo ↗
  • Chat & Chatbots overview Rate limits, join limits, the Chat Bot badge (granted when the broadcaster authorizes a Channel Chat Message subscription with an App Access Token and the channel:bot scope) and the verification pause ↗
  • Twitch IRC irc://irc.chat.twitch.tv:6697 or wss://irc-ws.chat.twitch.tv:443. Request the tags and commands capabilities to get ROOMSTATE, USERNOTICE and emote positions. We read chat with an anonymous justinfan login, which worked but is not described in the docs; use it only to prototype and switch to an authorized bot for the build you submit ↗
  • OpenAI Codex Start one thread for the project and keep most of the build there; you submit that thread's session ID ↗
  • TwitchDev Discord The organizers' help channel is #codex-twitchcon-hackathon ↗

Timeline

  1. Submission period opens (10:00 am PT)
  2. Submission deadline (2:00 pm PT); drafts lock after this
  3. Judging opens (9:00 am PT)
  4. Judging closes (5:00 pm PT); winners announced on or around Nov 15 at TwitchCon San Diego

How a beginner can ship

  1. Check eligibility

    Read section 3 of the rules. Organizations and residents of the excluded places cannot win.

  2. Open the Codex thread first

    Start a fresh Codex thread for the project and note its session ID from /status. Record a few minutes of screen while Codex builds, since the video must show that.

  3. Get the Example Chatbot running

    Create an app on dev.twitch.tv, get a token with user:bot, user:read:chat and user:write:chat, and make the HeyGuys to VoHiYo reply work in your own channel. Everything else builds on this loop.

  4. Budget the bot's voice

    Assume 1 message per second and 20 per 30 seconds. Batch replies into one summary message per window, and never repeat the same text within 30 seconds.

  5. Handle room modes

    Read ROOMSTATE and test your project with slow mode and emote-only mode switched on in your own channel.

  6. Get real viewers on camera

    Join the raid swap on the hackathon forum before Nov 1 or ask a streamer friend, so the video shows people using the project live on Twitch.

  7. Cut a video under 3 minutes

    Twitch footage first, then the Codex footage, then one sentence on what the streamer gets. Upload it to YouTube as public.

  8. Submit before Nov 2, 2:00 pm PT

    Repo with run instructions, description with how you used Codex, session ID and video link. Save a draft early: nothing can change after the deadline.