Google GitGoogle Git
Sign in
chromium/devtools/devtools-frontend/refs/heads/chromium/7989
commit
19c6eb23c68b06ed86c93443699f6ab4d3782de3
[log]
author
Jack Franklin <jacktfranklin@chromium.org>
Fri Jul 31 11:09:32 2026
committer
devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Fri Jul 31 12:27:53 2026
tree
00539a14ff959d49cd9f950070e61c49dec8d0bf
parent
6d398bed8c573b9c82097f37411d985095bfffb9 [diff]
AI: Split AI Assistance tools into DataTool and ContextTool variants

Separate the generic `Tool` interface into explicit `DataTool` and
`ContextTool` types and rename legacy `FunctionCallHandler*` result
interfaces to `Tool*Result`.

Previously, `Tool` collapsed data-producing tools and context-switching
tools into a single interface, obscuring expected return handler
contracts and type guarantees. Additionally, result type names used
verbose, legacy `FunctionCallHandler*` prefixes.

Splitting `Tool` into `DataTool` and `ContextTool` explicitly
distinguishes tools returning structured data payloads from those
yielding new conversation context targets. `Tool` is redefined as a
discriminated union of both variants, and `BaseTool` is parameterized
with generic tool arguments to share parameter schema logic. The result
interfaces are renamed to `ToolDataResult`, `ToolContextResult`,
`ToolErrorResult`, and `ToolApprovalResult` to standardize naming across
the framework.

Fixed: 540760036
Change-Id: I1169f16ef417172c0370d94b3ade2d2d11910389
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8176346
Reviewed-by: Alina Varkki <alinavarkki@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
14 files changed
tree: 00539a14ff959d49cd9f950070e61c49dec8d0bf
  1. .agents/
  2. .gemini/
  3. .github/
  4. .vscode/
  5. build_overrides/
  6. config/
  7. docs/
  8. extension-api/
  9. extensions/
  10. front_end/
  11. inspector_overlay/
  12. mcp/
  13. node_modules/
  14. scripts/
  15. test/
  16. third_party/
  17. v8/
  18. build
  19. buildtools
  20. .clang-format
  21. .clang-format-ignore
  22. .editorconfig
  23. .env.template
  24. .geminiignore
  25. .git-blame-ignore-revs
  26. .gitallowed
  27. .gitattributes
  28. .gitignore
  29. .gitmodules
  30. .gn
  31. .mailmap
  32. .npmignore
  33. .npmrc
  34. .style.yapf
  35. .stylelintignore
  36. .stylelintrc.json
  37. AUTHORS
  38. BUILD.gn
  39. codereview.settings
  40. CONTRIBUTING.md
  41. DEPS
  42. DIR_METADATA
  43. eslint.config.mjs
  44. favicon.ico
  45. LICENSE
  46. OWNERS
  47. package-lock.json
  48. package.json
  49. PRESUBMIT.py
  50. README.md
  51. SECURITY.md
  52. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.

Source code and documentation

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.

Source mirrors

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.

Getting in touch

There are a few options to keep an eye on the latest and greatest of DevTools development: