Skip to content

extension_theme_verify ​

Verify a Chrome theme manifest headless: the colors Chrome would paint and the keys it discards.

Quick start ​

Does this theme manifest paint the colors it declares?

Asked whether a theme is valid, the agent verifies the manifest and reads the verdict.

Asked whether a theme is valid, the agent verifies the manifest and reads the verdict.

Reference ​

Grouplocal, on by default
TierSee
Needsnone
Read onlyyes
Destructiveno
Idempotentyes
Reaches the open webno

Inputs ​

InputTypeRequiredDefaultWhat it does
manifestobjectnoTheme manifest object; or manifestPath.
manifestPathstringnoPath to a theme manifest.json.

Next ​

  • MCP server: install, the two groups and the session gates
  • Install in your client
  • extension_analyze: Analyze a BUILT extension in dist/<browser>: sizes, entries, permissions, store checks (not on a dev build).
  • extension_doctor: Diagnose a dev session leg by leg, each with its remediation; run it first when an act tool errors unexpectedly.
  • extension_dom_snapshot: Take a shallow DOM snapshot of one open surface or targetId, or list what is open (listTargets on the debug port, listTabs).
  • extension_inspect: Inspect a web page (or targetId) over the debugger protocol: HTML, DOM, console, probes, closed shadow roots.
  • extension_list_extensions: List the extensions in a session's browser; its own carries ownExtension:true.
  • extension_logs: Read a dev session's logs from every context in one timeline, or follow:true for live frames after the replayed ring.
  • extension_manifest_validate: Validate a manifest.json across browsers; buildBlocking lists the errors that make extension_build refuse.
  • extension_screenshot: Take a .png of one open surface, page or targetId in a live session (Safari: pages only); open it with extension_open first.