Skip to content

[FEAT] Inquiry: Support for Chrome DevTools Protocol (CDP) #75

Closed as not planned

Description

@wang25669

Is this a new feature request?

  • I have searched the existing issues

Wanted change

First of all, thank you so much for maintaining this amazing project! It has been incredibly helpful to me.

I am writing to ask if this Chromium image currently supports the Chrome DevTools Protocol (CDP)? If it is not currently supported, would it be possible to consider adding support for it in future releases?

Reason for change

Enabling CDP support would allow users to connect to the browser instance for automation, remote debugging, and testing (for example, using tools like Puppeteer or Playwright). This would greatly expand the utility of the container for automated web workflows.

Proposed code change

No response

Activity

  1. github-actions commented on Jun 25, 2026

    @github-actions

    Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

  2. thelamer commented on Jun 25, 2026

    @thelamer
    Member

    This related ?
    #71

  3. LinuxServer-CI commented on Jul 25, 2026

    @LinuxServer-CI
    Collaborator

    This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

  4. phpmac commented on Aug 20, 2026

    @phpmac

    Following up on CDP: the missing piece for agent tooling is MCP (Playwright MCP / Chrome DevTools MCP), not just a reachable DevTools port.

    CDP still binds 127.0.0.1 (#71) and needs a non-default --user-data-dir. MCP clients need Streamable HTTP, e.g. http://host:8931/mcp.

    Opened the same request on the Google Chrome image: linuxserver/docker-chrome#19

    Is an official docker-mod or README sidecar (socat + mcr.microsoft.com/playwright/mcp --cdp-endpoint) on the roadmap, or is CDP-only the intended attach surface?

  5. thelamer commented on Aug 20, 2026

    @thelamer
    Member

    I have no idea what you are talking about.

    Here is how development works:

    You figure out what needs to be changed by changing that thing and testing it
    Then you put that change into a fork
    Then you open a pull request with that change

    So what needs to change about this docker container ?

  6. LinuxServer-CI commented on Sep 19, 2026

    @LinuxServer-CI
    Collaborator

    This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

  7. moved this from Issues to Done in Issue & PR Trackeron Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions