Creative Tooling
Opus Vela Studio
Record, edit and design in one project: a source-available creative workspace where human and agent operations meet the same editable model.
Outcome
Capture, Edit and Design share one revisioned workspace and typed operation surface across the human interface, MCP, SDK and CLI, keeping every meaningful change visible, validated and recoverable.
Media
Select any frame to enlarge
Live Studio product page
The current Studio product page, led by a real developer-preview capture and a clear distinction between what works today and what is not shipped yet.
Current application build
The current Studio home direction used across the redesigned product web. It keeps the application itself at the centre of the story. The source graph, canvas, inspector and timeline address the same editable project instead of handing flattened files between separate tools. - Ready
An agent rewrites the headline twice over MCP while the editor is open. The canvas and the history update live, and every change is attributed — agent or you — in one revision sequence. Recorded by driving the running application. Home. The capability list is rendered from the same definitions the MCP server advertises, so it cannot drift from what an agent can actually call. Edit. A trim drag emits exactly one typed operation at pointer-up — the identical operation an agent submits. Selective revert. Any single change can be reversed without rewinding what came after. The middle entry is refused because a later edit touched the same object. Capture planning and consent controls. The current repository has since progressed into real capture authorisation and recording operations; this earlier screened image remains a truthful view of the project surface. Frame-snapped trim handles on a selected clip. Review opens on Activity: what changed, and who changed it.
Case study
The problem
Creative tools were not built for a world where an agent is a second pair of hands. Opus Vela Studio is built around a semantic control plane: natural language may propose work, but only typed operations can change project state.
Architecture
One unified scene/timeline project model sits behind one application-service boundary shared by the human interface, MCP, SDK and CLI adapters. Every mutation carries an expected revision and an idempotency key, so a stale write is refused rather than silently overwriting a concurrent edit, and a retried request cannot apply twice. Long work becomes a durable job that survives restart, and a completed render means the output file was probed — not that a model reported success.
One project, three pillars
Capture enforces consent and records source intent; Edit provides a real timeline, transitions, audio mixing, keyframes, speed ramps and silence analysis; Design provides a canvas, layers, masks, type, brand components, templates and export. All three use the same project truth instead of handing files between disconnected tools.
Where it is now
The local developer preview has working Capture, Edit and Design foundations behind the shared semantic kernel. Media is quarantined and probed before entering the trusted store; long work becomes durable jobs; selective history can reverse one operation without rewinding everything after it. Studio and Complete can now be purchased through the shared account and billing system, while a public signed Studio installer, hosted persistence and production cloud rendering remain later release work.
Verified architecture
System map
Technology
- TypeScript
- React
- MCP
- SQLite
- FFmpeg
- JSON Schema
- Local-first architecture
Scope and boundaries
Opus Vela Studio is a source-available developer preview under Elastic License 2.0 with a private repository; source access is arranged on request. The local capture, edit and design foundations and account-backed Studio and Complete plans are live. The site still makes the distribution boundary explicit: there is no public Studio installer or production cloud-rendering service yet.