03 / Writing & point of view
The work should outlive
the agent.
Better models make more work possible. My bet is that lasting product value also comes from the environment around them: shared context, trustworthy actions and work people can keep improving.
That shapes how I’m building to.video’s own agent harness. A cut, its source media, a team’s feedback and the history of decisions have to remain useful when a run stops, a teammate takes over or the model changes.
Make the domain legible
A coding agent reads a repository; a video agent needs picture, sound and an evolving timeline. Context and tools should reflect the actual work.
Keep control in the product
People need to inspect changes, guide the agent and recover earlier work. Permissions and history need to hold as models and runs change.
Count the complete job
I care about the finished result, revision effort, reliability, latency and total cost. That is what connects agent capability to a useful product and a viable business.
I see related design problems across domains: OpenAI’s engineering environments expose software and feedback to agents; Intercom’s Fin brings human decisions into automated support; durable execution preserves progress through failures and waits. The details differ. In video, I’m applying these ideas to shared, editable work—and the judgment needed to make it worth watching.