Is your feature request related to a problem? Please describe.
I am trying to annoate the video with specific timestamps that are accurate.
Describe the solution you'd like
I'm building an annotation layer on top of screencast. Overlaying timed markers (pass/fail, click highlights) on the recorded video. The challenge is syncing annotation timestamps to video time.
screencast_start is async. By the time the MCP response comes back, the video has already been recording for 1-5s. So I can't reliably compute "second 0" of the video from the caller's side. Setting t0 before the call is too early, after the response is too late.
Looking at the source, Puppeteer's ScreenRecorder subscribes to Page.screencastFrame events which include metadata.timestamp. It uses these internally for frame duplication but never exposes them.
Ask: Could screencast_start's response include the wall-clock time (or CDP timestamp) of the first frame? Something like:
{
"content": [{ "text": "Recording started...", "firstFrameTimestamp": 1718488800.123 }]
}This would let callers precisely correlate external events to video time without needing a direct CDP connection.
Describe alternatives you've considered
I built my own recorder that gets added to the toolset. Currently instead of using screencast_start and screencast_stop, I have a proxy mcp that my agent calls which then wraps the chrome devtools mcp. this proxy mcp opens a child process which is the real chrome devtools mcp. tools that are standard to the mcp are forwarded and tools that are related to recording is handled by this proxy server instead. from my own screen recorder i pass back the first frame timestamp which allows me to accurately set this beginning timestamp.
Additional context
No response
Is your feature request related to a problem? Please describe.
I am trying to annoate the video with specific timestamps that are accurate.
Describe the solution you'd like
I'm building an annotation layer on top of screencast. Overlaying timed markers (pass/fail, click highlights) on the recorded video. The challenge is syncing annotation timestamps to video time.
screencast_startis async. By the time the MCP response comes back, the video has already been recording for 1-5s. So I can't reliably compute "second 0" of the video from the caller's side. Setting t0 before the call is too early, after the response is too late.Looking at the source, Puppeteer's ScreenRecorder subscribes to Page.screencastFrame events which include metadata.timestamp. It uses these internally for frame duplication but never exposes them.
Ask: Could screencast_start's response include the wall-clock time (or CDP timestamp) of the first frame? Something like:
{ "content": [{ "text": "Recording started...", "firstFrameTimestamp": 1718488800.123 }] }This would let callers precisely correlate external events to video time without needing a direct CDP connection.
Describe alternatives you've considered
I built my own recorder that gets added to the toolset. Currently instead of using screencast_start and screencast_stop, I have a proxy mcp that my agent calls which then wraps the chrome devtools mcp. this proxy mcp opens a child process which is the real chrome devtools mcp. tools that are standard to the mcp are forwarded and tools that are related to recording is handled by this proxy server instead. from my own screen recorder i pass back the first frame timestamp which allows me to accurately set this beginning timestamp.
Additional context
No response