NEWTimelineEdit the story
after the take.
Zooms, effects, captions, sounds, and cuts live on one timeline — playhead, split, undo, and save without a full NLE.
Works where Cursor & Claude already live
Cursor
Claude
MCP
Chrome
WindowsThe problem
Every demo starts from scratch.
Re-doing timeline by hand on every take
Opening a full editor for a thirty-second demo
Agents that capture clicks but leave the polish to you
The fix
Timeline is built into the studio — not bolted on later.
01One timeline, many lanes
Auto pipeline drops polish on stop — then you nudge markers, trim beats, and keep what serves the story.
02Keyboard-first
Space to play, arrows to nudge, Z for zoom, C to cut, Delete to remove — built for fast demo iteration.
03Save as a project
`.yasharka` keeps styling, markers, and polish metadata so you can reopen and finish later.
In the studio
The real Screen Beaver UI — Timeline selected.
Rail, inspector, stage, and timeline — the same chrome you get in the desktop app and the web demo.
Set up once & you’re done.
The only step that needs you is the first one.
01 Connect once
Install the MCP server. About thirty seconds.
$ npx @screenbeaver/mcp
02 Keep your tools
Cursor, Claude Desktop — nothing to switch.
03 Ship the demo
Timeline lands on the timeline — export locally.
Same demo. Different finish.
Toggle timeline on — watch Screen Beaver do the polish work between a raw take and a shippable cut.
Studio · Timeline
On
Portable. No lock-in. Local export.
On the timeline
Nudge, delete, or regenerate — nothing locked after the take.
Delete anytime
Remove markers you don’t want. Your project stays yours.
Export locallyNEW
H.264 MP4 on your machine. No cloud encode required.
One studio · every demo
Stop scrubbing for timeline.
Free to start. Wire MCP once — then ask Cursor or Claude to film while timeline lands on the timeline.
