Using "dynamic workflows" in claude a bit too intense I guess
> API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited
just added a more interactive demo #flappybird
Built a tiny browser engine for fun 🦀 → 🕸️ It parses, styles, lays out (taffy), scripts (QuickJS) and paints (tiny-skia) HTML/CSS/JS entirely inside WebAssembly. The browser never sees the markup - only pixels come back out.
jot.skorfmann.com/prism-render...
and of course, the video itself was also created via ai helmut.rocks/making-of.html
The compiled wasm for the browser is about 2.5 mb and runs and renders arbitrary JS, CSS (subset) and HTML
A fun experiment I'm pursuing with Codex, building a simple browser rendering engine within a browser via Rust / WASM - Latest and most sophisticated take so far: play a video file with sound and do all the work in wasm. Codex runs for more than 16 hours already, and it's getting there
A titanic simulation 🚢 #fable5
jot.skorfmann.com/titanic/
> Meet Fable 5, our newest model for complex, long-running work. Try anytime with /model.
> Included in your plan limits until Jun 22, then switch to usage credits to continue.
www.anthropic.com/claude/fable
👀
Dynamic Workflows in Claude Code to non coding problems are superb for fanning out 100s of subagents in minutes.
running codex in multiple subsequent "/goal" loops for the last 24 hours - so far no limit in sight