Repository navigation
v1.2.0
Adds Chrome 155 compatibility while preserving existing 1.x polyfill behavior.
Library
document.modelContext.executeTool()defaults to a fresh{}when both input and options are omitted orundefined. Calls with options still require an input object.- Object inputs continue to pass by reference, with existing input errors and cancellation precedence preserved. Native Chrome 155+ serializes object inputs, so use plain JSON-compatible objects for portable calls.
- Legacy JSON-string inputs remain supported in 1.x. Deprecation is planned for 2.x, without removal in 2.x. The React hook's
execute()API is unchanged.
Bridge extension 0.2.2
- Supports Chrome 155 object inputs, older native JSON-string APIs, and legacy polyfills without retrying user tools after handler errors.
- Includes the hash-navigation and persisted-activation fixes from 0.2.1.
The Chrome Web Store update is distributed separately. webmcp-server remains at 0.2.0.
Validated with 299 tests and browser smoke tests on Chrome 153, 155, and 156, including tool discovery, execution, and cancellation.
Full changelog: https://github.com/agentcathq/webmcp-react/blob/v1.2.0/CHANGELOG.md