Fix Nemotron storyboard planner and add reset/PDF export features
Session from build-small-agent-trace on Hugging Face by drdavidtang · MIT · condensed by Coders Talk
Click a segment to jump to that moment
35msession
0interventions
GOAL
Fix a failing storyboard planner that sometimes returned the wrong number of scenes, then extend the app with a warm-start for the model container, a reset-to-start control, and a PDF export of the finished storyboard.
- +0Prompt · +0Nemotron planner throwing 'Planner must return exactly four scenes' and returning 502; also asked to warm the container on app load and add a fallback to a lightweight model if nemotron fails
- +0Agent did · +0Reworked storyboard planning to add a fallback lightweight model with split-task calls for the 1B model, warmed the nemotron container on first app load, verified the live endpoint by hitting it directly, then committed and pushed the change (commit 5ab4ab1)
- +8mPrompt · +8mAsked whether storyboard state is per-user (frontend only) and how a user resets back to the start screen
- +8mAgent did · +8mConfirmed state lives only in React state per browser tab, then added a reset/new-story control that clears storyboard, history and terminal output and returns to the intro screen; committed and pushed (commit 11ae83d)
- +35mPrompt · +35mSaid the ending felt flat once a user finished exploring the storyboard and suggested offering a PDF download of it
- +35mAgent did · +35mImplemented a storyboard PDF export (new backend/pdf_export.py plus tests), committed the change (daa4993) and pushed it to the Hugging Face Space remote
- +35mOutcome · +35mThree commits shipped to main: nemotron planner fix with fallback model, a reset-to-start control, and a PDF export feature, each pushed to the Hugging Face Space remote
VERDICT
Next time I'd bundle the reset control and the PDF export into the original brief since they came from the same 'what happens after the storyboard finishes' train of thought, instead of asking for them one at a time. The fix that actually mattered was making the planner fall back to the lightweight model when nemotron returned the wrong scene count — that's what killed the 502s.