-
-
The viewer receives Joseph’s approved clarification, labelled Creator note.
-
Actual creator view: microphone capture continues while automatic publication is paused.
-
Full history shows the one genuine recorded stream, dated 1 November 2026.
-
Actual Brotato broadcast: CatchUp’s latest three context entries advance while gameplay continues.
-
Product illustration: timeline with fictional WillowbrookDemo data.
-
Product illustration: dated history with fictional example streams.
CatchUp
Arrive midstream. Understand the story.
Inspiration
I started this project as someone new to Twitch. Joining an unfamiliar stream gave me video and chat, but little sense of the conversation or what had led to it. I wanted to understand enough of the story to join in.
What it does
CatchUp brings the creator, current activity and recent published moments into one readable timeline beside Twitch. The live view follows the latest three updates. Browse earlier moments, inspect their source times, or open Full history for connected streams with their original dates.
The Windows creator companion connects to Twitch, records the selected microphone while the verified channel is live, transcribes speech locally and generates source-checked context. Creators choose capture and publication, can add reviewed clarifications, and deliberately resume automation after a manual pause. Full recordings, transcripts and drafts stay local; transcript excerpts require a separate sharing choice.
On-air names are creator-confirmed and tied to a broadcast and time interval. Joseph taking over from Georgie does not rename Georgie’s earlier entries.
Built with Codex
I directed the newcomer problem, product flow, design and testing. Codex helped build the Python/FastAPI/SQLite backend and React/TypeScript viewer, investigate failures, and write regression checks. The demo includes my actual recorded Codex development work.
One useful fix freezes the evidence being checked, allowing new speech to arrive without discarding every recap. A concurrent creator correction still invalidates stale output. Other safeguards bind context to its broadcast, check quoted evidence, preserve publication history and respect transcript permissions.
The real test
We ran CatchUp during a real Brotato broadcast on my Twitch channel, joseph_o17, on 1 November. Selected microphone audio reached local transcription, automatic context publication and the viewer. The demo shows the three-entry window advancing while gameplay continues, real history navigation, and an approved creator clarification reaching the viewer with automation paused and then resumed.
The correction was saved in the creator interface and published through its local owner API after the first UI attempt hit a routing error; the submitted source fixes that route. Two reloads left measured capture gaps of about 62 and 66 seconds while OBS kept broadcasting and recording. The run therefore has partial audio coverage.
Challenges and next steps
Source checks reduce mistakes; they do not guarantee accurate summaries. The pilot exposed uncertain wording and ASR errors, and the creator clarified an item’s expected effect rather than claiming it had been demonstrated. Comprehension, retention and creator workload benefits still need testing with unfamiliar viewers.
The demonstrated route is the local companion beside Twitch, including an OBS annotation. The separate official Extension remains in Hosted Test, without completed native-live acceptance or public approval. Local processing used a pinned qwen3:32b model on an RTX 5090 with 32 GB VRAM and 64 GB RAM; that is the tested configuration, not a measured minimum.
Judges can watch the demo and browse the dated context snapshot without installing the model. The matching Windows download and setup guide provide the local creator route. I want to improve onboarding and summary quality before expanding beyond the pilot channel.
Built With
- codex
- fastapi
- faster-whisper
- ollama
- python
- react
- sqlite
- twitch
- typescript