[AI] Use full trace agent for insights AI feature This replaces the original insights agent with the new, "full" trace agent, and removes the support code that is no longer needed. * when providing context to the agent, instead of directly including the insights summary in the initial query via enhanceQuery, denote that the user just clicked a specific insight. The trace summary will have some details about the insight, and the agent reliably calls getInsightDetails to learn more. * ensure createBounds never produces invalid bounds. * stop giving so much data to BaseInsightComponent to support the AI feature. Instead, just give it an agent focus directly. Bug: 442392194 Change-Id: Id3e03a7f66b672684c1e21d39dcc65aa919bd346 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6914156 Commit-Queue: Paul Irish <paulirish@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.