Stream Assist

Inspiration

Streamers divide their attention between the activity on screen and a fast-moving chat. I wanted create an assistant which can respond to the viewers, make them noticed and also murdered the entire chat while the streamer is doing his thing like playing a game.

What it does

Stream assist is a codex plug-in where streamers can connect their account and then use Codex as an assistant ex reply to messages this will increase engagements and not give the viewers the feeling of being ignored when the streamers is busy or completely moderate the entire chat. The streamer can instruct the agent/Codex to moderate the users or reply to certain messages like what the game details or any hardware, for example, what mouse they are using and then maybe also provide affiliate links in the chat so that we can go directly to the product page and make a purchase. It's a win-win situation for both increase interactivity. Nobody gets ignored and streamer, also make some extra money. This is the initial version which just interact with chat. They can also do other things that are possible with Twitch API such as changing title of the stream or manage schedules or create a poll the possibilities are endless. The streamer can build his own app on top of this plug-in in the codex.

How we built it

The implementation uses JavaScript, Node.js 24, the official Model Context Protocol SDK, Zod, Twitch EventSub WebSockets, Twitch's Helix chat API, and Twitch's device authorization flow. We bundled runtime dependencies so the installed connector does not rely on the development folder's node_modules.

Codex specified the architecture, reviewed implementation, integrated browser authorization, corrected plugin packaging and runtime paths, debugged filtering and connection behavior, added regression tests, and verified the actual Twitch connection and reply delivery. Codex authored the initial implementation and the device authorization module.

Installation

Ask codex to install this plugin https://github.com/VKR981/StreamAssist

Challenges we ran into

The first version incorrectly ignored all messages from the authenticated streamer, including test commands. We fixed it to accept explicit !ask commands while rejecting that prefix in outgoing replies to avoid self-reply loops. We also changed new filter settings to replace earlier rules, preventing an old questions-only filter from silently blocking a greeting command.

Other work included EventSub reconnection and subscription lifecycle handling, cancellation, bounded queues, safe local credential storage, and verifying Twitch's is_sent field rather than assuming HTTP success means a message was posted.

Accomplishments that we're proud of

I was able to build this plug-in in a day, thanks to Codex and detailed documentation of Twitch API

What we learned

This was the first time me building a Codex plug-in, I learnt a lot about Codex plugins and MCP servers , and what are the challenges, extensions, and apps are available for Twitch streamers

What's next for Stream Assist bhejo

I think Stream Assist is just the beginning. It opens the doors for endless possibilities. Anyone especially streamers can build their own apps on top of this plug-in using codex and Twitch API.

Built With

• api
• codex
• javascript
• node.js
• twitch
• zod