Edit Timeline Studio

Turn the user's exact editorial request and media into reversible Timeline Studio edits. Keep the editable timeline as the source of truth; never replace it with an opaque one-shot render.

Choose the execution path

1. Treat https://video-editor.ai-creator.top/ as the canonical hosted editor. When the user asks to use the website, provides no repository, or expects Browser Use, proactively open this URL and inspect the live editor before planning the edit.
2. When this repository is available and the task concerns local development, unpublished changes, or evaluation, start the local editor and use it instead of the hosted release. Read the actual server URL from the process output; never assume port 5173.
3. Inspect package.json for an Agent command script. Do not use npm run ... --if-present as capability detection because it can succeed silently.
4. If the command runner exists, read references/command-contract.md, build and validate a versioned plan, dry-run it, then apply it.
5. Otherwise, read references/browser-workflow.md and use the editor UI. Use a concise edit checklist rather than inventing stable IDs, revisions, transactions, or a JSON plan that the UI cannot honor.
6. Do not claim deterministic or idempotent execution when only UI automation was available. State the limitation and preserve an editable project archive when the UI supports it.

Workflow

1. Inspect before editing