You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: MCP startRecording over stdio reports a 30s timeout instead of the capture failure #1640
When the recorder fails to start, startRecording on the stdio MCP server waits 30 seconds and returns a generic deadline error:
The recording did not start: Error: Recording did not start within 30s — see stderr for the underlying capture error
The actual capture failure never reaches the client (here: "The ScreenCast portal does not advertise METADATA cursor mode, so real cursor positions cannot be obtained on this session."), and the response doesn't say whether sources, permissions, cursor negotiation or encoding failed.
Expected behavior
A start the recorder already knows failed should fail the call immediately with its reason; the timeout should be reserved for an outcome that is genuinely unknown — the same direction as #1205 and #1371.
To Reproduce
Arch Linux, Hyprland 0.56.2, xdg-desktop-portal-hyprland 1.4.1 (AvailableCursorModes = u 3: HIDDEN|EMBEDDED, no METADATA), native PipeWire helper, openscreen 2.3.0-1.
openscreen mcp over stdio; call startRecording with {"microphone":false,"systemAudio":false,"camera":false} (omitting cursor requests the default editable overlay).
The start fails in cursor negotiation; the tool returns the 30s timeout. Control: the same call with "cursor":"system" records fine.
This change is assigned to the Next Release release milestone and is not necessarily available in the latest downloadable desktop release yet. It is currently marked as status: pending release until a packaged release containing it is published.
Activity
github-actions commentedon Nov 21, 2026
Fixed by #1641 and merged into
main.This change is assigned to the
Next Releaserelease milestone and is not necessarily available in the latest downloadable desktop release yet. It is currently marked asstatus: pending releaseuntil a packaged release containing it is published.