The Hard Part of Long-Running Agents Is Not the Model
Description and use
Long-running video agents fail due to system design, not model quality. Key fixes include explicit state tracking, separating model proposals from deterministic code, robust budgeting, and stateless coordination.
Problem
Long-running AI agents for video production fail not because of model quality but due to system design flaws that mismanage state, budget, and execution flow.
Outcome
By treating the agent as a distributed system with explicit state management, deterministic execution, and robust budgeting, NoodleTomato achieved reliable, resumable, and cost-effective long-running video production.
Workflow
- 1. Receive brief and create initial plan
- 2. Model proposes shot list, narration, and render steps
- 3. Code validates proposals, checks permissions, reserves budget, writes committed state
- 4. Workers execute tasks, report status to artifact store
- 5. Coordinator remains stateless, wakes on job completion
- 6. After all tasks, run validation and audit outside agent control
- 7. If needed, replay state for debugging without re-running paid jobs
Evidence
The model did not hallucinate. It reasoned correctly from an incomplete snapshot.
The model should never grant itself a capability, approve its own output, or author the amount shown on a billing card.
- Record date: 2026-09-15T12:45:52.560Z