[Ai] Allow more MAX_STEPS and return error message if limit is hit Previously the response that the Ai is stuck was only shown to the user if we had no requested function call, nor a text response and exceeded the max steps. However, if the last step was a function call request that succeeded, the model is still not done evaluating. In this case, output the error message related to max steps to the user. In the other cases, we can use the UNKNOWN error. In addition, increase the MAX_STEPS and add additional guidance for the agent to stop investigation and ask the user to select the element if it is within an iframe. Fixed: 564882090 Change-Id: I5a090ee0eacbcd6599a501c985752d0381b35bab Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8505504 Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Kim-Anh Tran <kimanh@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.