Skip to content

Error #62953

Open
Open

Description

@matizdz

Description

Error: Desktop IPC handler failed at ete (oc://renderer/assets/main-PFC26dD0.js:2:44788) at $ee (oc://renderer/assets/main-PFC26dD0.js:2:44474) at MessagePort. (oc://renderer/assets/main-PFC26dD0.js:2:43867) at MessagePort.i (oc://renderer/assets/esm-rub_JZLD.js:15:6665) ──────────────────────────────────────── Causé par : { "name": "UnknownError", "message": "An error occurred in Effect.tryPromise", "cause": { "name": "Error", "message": "Background service failed to start" } }

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot

No response

Operating System

No response

Terminal

No response

Activity

  1. opencodejr commented on Nov 9, 2026

    @opencodejr

    Thanks for the report, @matizdz! (Feel free to reply in French.)

    Background service failed to start is a generic message. It means the Desktop app's background service started but then reported that its own startup failed, and the real cause isn't in this error. Several different problems end in this same message, so could you share:

    1. OpenCode version: shown in the Desktop app, or from opencode --version.
    2. Operating system, and how you installed the app (installer from opencode.ai, package manager, etc.).
    3. When it happens: on every launch, only after an update, after waking from sleep, or something else? Did an earlier version work?
    4. The service log: the most recent entries from opencode.log around the failed launch. It is in ~/.local/share/opencode/log/ (on Windows, %USERPROFILE%\.local\share\opencode\log\). If you have the opencode CLI, the output of opencode service stop followed by opencode serve --service --print-logs --log-level debug also helps. Please remove anything sensitive first.

    If it started right after an update, running opencode service stop and then reopening the app may get you going again (see #62326).

    Possibly related issues, ordered by likelihood:

    You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done editing.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions