Productions hold together better. The screenplay writes its scenes in steady batches and reports each part of the outline as it starts and finishes. Character, location and prop lists fill in from the screenplay. A cut refuses to leave a shot out, a run that comes up short says so and keeps its place, and a music video now starts a short film beside the music. One conversation can start a second production of a different kind.

Every generation is metered at what it really cost, so the numbers on the page match the work that was done. Buying extra credits and resets from the page is on the way.

Runs are sturdier underneath. One agent that hangs can be stopped without stopping the rest, and a cancelled agent restarts on its own without restarting the whole run.

Characters get their own studio on the assets page. An empty character frame shows an example sheet, so it is clear what a finished one looks like before you make it. Every generation in the studio now shows the same generate card, labeled by what it is making, and music can start straight from the production grid.

The chat can open an editor for you when you ask for one, and the editor you have open lives in the address, so a link to it opens the same view for anyone on the project. Chat pictures show at their own aspect ratio and fit the screen in full view.

To open a room, click Collaborate in the script's More menu. Anyone with editor access to the project can join. When a writer leaves, their cursor and name leave too.

Screenplays open in and out of the studio without losing shape. Import a script from another screenwriting app and edit it here. Export the finished piece as a Word document, a PDF, or a Fade In file. The layout that leaves is the layout that came off the editor's page.

Mobile Studio picked up a shape pass: two of its main rails are canonical across every screen now, so the mobile experience matches the tighter shape desktop already had.

The audio mixer used to be its own destination in the studio. It now lives inside the production pages, where the rest of the production work happens, so the mixer is where you would expect it while you are working on a piece.

Chat replies from the studio no longer use em-dashes. The model had been sneaking them into prose. They are stripped now, so the replies read the way the rest of the studio does.

The status page is now backed by a live pipeline. Component health, active incidents, scheduled maintenance windows, and the last ninety days of daily uptime are updated by the platform itself on a short interval, published to shared object storage, and served from a location that survives outages of the systems it reports on. A public feed is available too, so you can pull it into your own dashboards.

You can also subscribe by email to either status or changelog. It is double opt-in, so a confirmation link lands in your inbox after you sign up. The confirmation and unsubscribe pages are one click and no login is required. Status subscribers hear about incidents as they open, update, and resolve, and about scheduled maintenance when it is booked and when it starts. Changelog subscribers get an email each time a new entry ships on this page.

Full production manifests are no longer embedded into memory. They were being written to the vector store as-is on every finalize, which made retrieval noisy (a manifest is too big to be a good semantic hit) and cost real time on the write side. Skipping the embedding step keeps memory tidy and shaves time off every finalize.

And the non-film production workflows (novels, audiobooks, music, YouTube, and social) picked up their own optimization pass, matching the film work we shipped this morning so every content type finalizes on the same fast rails.

The vertical gutters that used to live on <main> moved onto the chrome itself, so the chrome carries its own margins and the main area is edge-to-edge. The header stopped floating: it is flat and static above the scroller now, so nothing floats over the content when you scroll. And the prompt rows above the composer picked up a real reusable component (the same look and behavior as the dock, plus a sticky push-away so a long prompt list does not shove the composer off the bottom).

Under the hood, the treatment and synopsis workers stopped needing tools (they were reaching for tools they never used), so those passes run cleaner and cheaper. And the whole workflow got audited for cost, with a set of guided output caps that stop runaway beat writers and scene jobs from overshooting.

Under the hood: the thinking budget is now floored engine-wide (a rare zero value was quietly producing empty replies), tool rounds no longer send a thinking budget at all (they need deterministic content), server-sent events terminate with the right double-newline (a single newline was letting some clients buffer past the end), a heartbeat across the whole request keeps long delegate rounds alive, and the stale job reaper now waits three minutes for the first token instead of forty-five seconds so slow first tokens do not get killed. Tool calls are preserved when the stream is reassembled, malformed template args no longer break dispatch, and sub-agents can run with no tools when the phase does not need them. On the studio side you should just see: chat feels solid, tools work, streams do not stop halfway.

LLM dispatch is now non-blocking, so a single slow stream no longer serializes every other request behind it. If one job takes its time thinking, everyone else keeps moving. And the image engine picked up separate step counts for its speed and quality lanes, so when you ask for speed you get a shorter render, and when you ask for quality the engine takes the extra passes to earn it.

The assets back button now re-squares the cached gallery instance when you activate the tab, so returning to Assets never leaves you looking at a stale view of what is there. The gen feed's prompt row is back after a brief absence, this time rebuilt on the canonical row shape so it matches everything else in the feed. And in every chat surface where Voysey shows its reasoning, the reasoning stream now forwards to the client cleanly, so intermediate thinking bubbles up as it is written instead of arriving all at once at the end (or dropping silently in the middle).

The images along the way now load one turn ahead of your reading, not all at once on first paint. The front page comes in more than half again lighter as a result (896KB down to 397KB). Backward turns picked up the same entrance curve the forward turn uses, so the page moves the moment you scroll instead of hesitating.

The Studio-to-Watch publish handshake now allowlists the content types it accepts on the way in (safer for a wire that stays scoped narrowly), and every product that lands on Watch keeps a persistent external reference back to the source production, so future syncs know exactly what they are updating.

Over on Books by Voysey, the preflight tray now advances to the edition picker the moment the LLM finishes its last question, instead of waiting a beat that could feel like a stall.

And the Instant model tier no longer sends a zero thinking budget in a rare edge case that could produce a crash on the model side. It floors the value to a safe minimum instead.

Live at books.voysey.ai. Early access means the surface is real and everything works end to end, but expect the shape of some pages to keep moving.

From "you can see the timeline" this morning to "you can cut a film with it" this afternoon.

Foundations went in today. The type system the editor will work against, a shared editor store that keeps state coherent across the editor's surfaces, and an audit of the existing film-editor primitives with a plan for what to port and what to replace. No UI to try yet. That is the next wave.

The panel also survives page reloads cleanly and shows a distinct failed-workflow card when a phase does not complete, with the retry action right on the card.

Drag any non-image file onto the dock and it goes straight to import. While Voysey classifies, the document gets a pending badge on the project so you can see it queued. Once classification finishes, the badge clears and the document lands in place, live, without needing to reload.

Alongside the takeover shell, the surrounding mobile chrome landed too: a proper page header with back and actions, a hero for the project overview, a stat-bar footer, and a read-only multitrack timeline in portrait for reviewing an arrangement.

Pick the channels that suit you: a notification in your browser at your desk, a push on your phone, a nudge from the desktop app, or a text message when you are away from a screen.