Skip to content

[Bug]: MCP startRecording over stdio reports a 30s timeout instead of the capture failure #1640

Closed

Description

@IdrisGit

Search existing issues

  • I have searched the existing issues

Describe the bug

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

  1. 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.
  2. openscreen mcp over stdio; call startRecording with {"microphone":false,"systemAudio":false,"camera":false} (omitting cursor requests the default editable overlay).
  3. The start fails in cursor negotiation; the tool returns the 30s timeout. Control: the same call with "cursor":"system" records fine.

Screenshots

No response

OS

Linux

OS Version

Arch Linux (Hyprland 0.56.2)

Other OS

No response

Browser

None

Browser Version

No response

Other Browser

No response

Device Type

Desktop

Other Device

No response

Additional context

No response

Activity

  1. added
    status: fixed in mainWork is merged into main but may not be in a downloadable release yet.
    status: pending releaseMerged change is waiting for a packaged desktop release.
    on Nov 21, 2026
  2. added this to the Next Release milestone on Nov 21, 2026
  3. github-actions commented on Nov 21, 2026

    @github-actions
    Contributor

    Fixed by #1641 and merged into main.

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingstatus: fixed in mainWork is merged into main but may not be in a downloadable release yet.status: pending releaseMerged change is waiting for a packaged desktop release.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions