Now that “Scene 0” works as a tutorial, next step is building the start menu and a save system for upcoming chapters and scenes. Step by step 💪
#vibecoding#gamedev#threejs
Here we go again!!! Codex UI (where chapters and lore will live) with placeholders for now. Getting more excited with every new feature added!
Everything coded with GPT-5.3-Codex + Three.js, and UI assets generated with Nano Banana Pro + Meshy (3D characters) + Hailuo (background loop) + ElevenLabs (voices and sounds). We keep building! 🥳
GPT-5.4 Thinking and GPT-5.4 Pro are rolling out now in ChatGPT.
GPT-5.4 is also now available in the API and Codex.
GPT-5.4 brings our advances in reasoning, coding, and agentic workflows into one frontier model.
GPU GIVEAWAY
Buy a GPU × GTC 2026 = Give a GPU
> RTX PRO 6000 Blackwell
> 96GB VRAM • NVFP4
> ~$15K value
> Brand new
If this does well I’ll ask NVIDIA for more GPUs next time… maybe even DGX Sparks
How to enter?
Short clip here
Full clip in the replies
GO GO GO
Codex 0.107.0 is here, and with it: FORKS🍴
This minor update includes the ability to fork your current chat history directly with custom multi agents with just a quick prompt.
"Fork this session using n subagent(s)"
This unlocks some interesting use-cases where you can launch multiple agents that retain all of your chat history up to that point, each in their own independent session.
For example, you've been discussing architecture with Codex for 20 minutes, talked through constraints, reviewed existing code, settled on a model.
Now you want to see two different implementation strategies side by side. Fork lets both children start from that full shared understanding.
With a normal spawn, you'd have to re-explain the entire context to each child, and they'd inevitably miss nuance from the earlier conversation - which is basically a form of compaction/compression.
With something like this, you could also just tell it to fork itself 5 times, and implement the same UI/frontend 5 different times in their own worktree to see which one you like the most.
Other potential uses:
- branching after reviews
- try and rollback patterns using worktrees
- parallel debugging strategies
Otherwise, this is a minor update with improvements to the app server, realtime transcription, and memory.
Enjoy!
Now that “Scene 0” works as a tutorial, next step is building the start menu and a save system for upcoming chapters and scenes. Step by step 💪
#vibecoding#gamedev#threejs