Skip to content

[Bug]: MCP getFrames cannot read a GIF export ("media error 4") #1215

Closed

Description

@EtienneLescot

Platform: macOS 26.5 (M1), CI build of main @ 0bed36852 (run 38581408372). It fails on both the stdio and the in-app HTTP server. Found during the e2e pass logged in #1212.

Repro

  1. exportVideo with path: "/…/out.gif", gifSize: "small" (succeeds: 852×480, 15 fps).
  2. getFrames with projectId of that project (its last export is the GIF), or with path to the GIF.

Expected: frames from the GIF, as for an MP4. The server instructions tell the agent to "exportVideo, and getFrames with the projectId to check the export before you hand it over".

Actual: Chromium could not decode the video (media error 4) on both servers. The same project exported to MP4 gives frames normally.

Impact: the documented check-before-handing-over flow fails for every GIF export. An agent that follows it gets an error and no way to look at what it made.

Direction: decode GIFs another way (an <img>/ImageDecoder, or ffmpeg, which the app ships), or check the GIF's MP4 sibling. At the least, say plainly that getFrames does not read GIFs, both in the tool description and in the error.

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 Oct 14, 2026
  2. added this to the Next Release milestone on Oct 14, 2026
  3. github-actions commented on Oct 14, 2026

    @github-actions
    Contributor

    Fixed by #1227 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.

  4. added a commit that references this issue on Oct 14, 2026
  5. added a commit that references this issue on Oct 15, 2026
    3823809
  6. EtienneLescot commented on Oct 15, 2026

    @EtienneLescot
    MemberAuthor

    Moved into v2.1.0 as part of the pre-release cut.

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

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions