Skip to content

DevTools Discovery API integration #2553

Open

Description

@swissspidy

Feature Description

See https://developer.chrome.com/blog/devtools-for-agents-3p-tools and https://developer.chrome.com/docs/devtools/agents/use-cases/third-party-tools

Exposing WordPress internal state this way would facilitate AI-assisted performance debugging.

See also WordPress/ai#760

Activity

  1. moved this to Not Started/Backlog 📆 in WP Performance Ongoingon Jun 30, 2026
  2. westonruter commented on Jul 2, 2026

    @westonruter
    Member

    Seems like this is a new take on the HTML Source Maps idea. Closely related to Server-Timing and the Origination project I started (and didn't finish).

  3. swissspidy commented on Jul 6, 2026

    @swissspidy
    MemberAuthor

    HTML Source Maps is just one angle for this. The imperative API offers a much more generalized way of providing runtime info from the page's JS to DevTools. For example cache hits/misses, database queries made, phpinfo, or even tools such as troubleshootPlugin, makeDatabaseQuery.

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

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions