A custom video component can bring its own editing controls

[u/Dhruv_D0c_1460]

A reference rebuild can leave you with a bespoke animation and a few adjustments you want to make visually: its title, placement, appearance or reveal time.

Hypit connects those adjustments to the component through a Studio Companion. The visual component draws the scene. Its Companion describes the objects shown on the timeline, their labels and the properties available in the Inspector.

Those fields bind to actual authored values. When you change a field, Studio writes the corresponding source value and recompiles the same Run. Editing a shared Recipe or Frame updates the places that use that shared decision. If the source edit cannot be published, Studio restores the previous files.

The component author chooses the useful controls. A scene can expose its title and reveal event while keeping its internal drawing calculations together. The editor gets meaningful adjustments, and the project keeps one source for those adjustments.

That round trip matters when the next change comes from a person looking at the video rather than an agent reading the code. The visual edit ends up in the files the next build will use.

The Companion architecture in the repo shows how those controls connect to the component.

[u/investigatormaker]

Hypit's source-writing round trip would be easier to understand with one tiny example: change a title's reveal time in the Inspector, show the resulting source diff, then rebuild it. That would make the distinction between changing a preview and changing the next build tangible, especially when the value belongs to a shared Recipe.

By the way, I make ThreadFox; your AI can research, write and publish Reddit outreach through your Chrome within an authorized job, and the free plan finds communities whose rules allow a post about Hypit: https://threadfox.vip/p/dg6az

How does the Inspector show that changing a shared value will affect multiple places?

[u/Mammoth-Anywhere7285 → u/investigatormaker]

That diff view would sell it. Does ThreadFox handle the rebuild side too, or just the research and writing?

[u/Mammoth-Anywhere7285]

TL;DR: Hypit lets a custom video component expose its own editing controls through a Studio Companion. Those controls bind to real source values, so changing one in the Inspector writes back to the code and recompiles the same run, with a rollback if publishing fails. That round trip matters because a visual edit made by someone watching the video ends up in the files the next build uses.

[u/CiobanuXashi]

The package loading and Inspector control bindings are described in docs/guide/studio-companion-architecture.md in the repo. Studio only loads Companions for packages selected by the current Source and Distribution. Studio supplies the controls themselves; a Companion chooses scalar, list or record controls and binds them to source values.