[BUG] CoWork Chrome/computer-use tool fails with parameter type errors when browsing Looker Studio dashboards

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When using CoWork to browse a Google Looker Studio dashboard, the Chrome tool (computer-use/browser) fails with parameter type errors. CoWork correctly identifies that it should use the Chrome tool to access the dashboard, but cannot successfully execute the browser action due to type mismatches in the tool parameters.
CoWork reports it is "having issues with Chrome tool parameter types" and "can't find the right parameter format" for computer-use. It then falls back to other available data sources, but the Looker Studio-specific data is lost from the workflow.

What Should Happen?

CoWork should be able to navigate to a Looker Studio dashboard URL using the Chrome tool, wait for the page to render, and read the visible data from the dashboard — similar to how Claude in Chrome (the browser extension) can browse authenticated Google pages.

Error Messages/Logs

The exact error output was not captured in logs, but CoWork's own status messages during the attempt were:
"I'm having trouble with the Chrome tools due to type issues"
"I need to request access for computer-use but can't find the right parameter format"
(No stack trace was available — CoWork handled the failure internally and moved on.)

Steps to Reproduce

1. Open CoWork in Claude Desktop (macOS)
2. Provide a task that requires reading data from a Looker Studio dashboard
3. Include the Looker Studio URL (e.g., [https://lookerstudio.google.com/u/1/reporting/[report-id]/page/page-id])
4. Ensure you are signed into Google in Chrome so the dashboard is accessible
5. CoWork recognises it needs to use the Chrome/browser tool
6. CoWork attempts to invoke the Chrome tool but fails with parameter type errors
7. CoWork reports "Chrome tool parameter types" issues and falls back to other data sources

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.1.8359 (64248d)

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This is being used as part of an automated client reporting workflow where Looker Studio contains WhatConverts call tracking data and blended cross-channel metrics not available from the underlying APIs (GA4, Google Ads, Meta, GSC) individually.
Looker Studio dashboards are JavaScript-heavy and may need extra rendering time — the Chrome tool may be timing out or failing to construct the correct interaction parameters for a complex SPA page.
The dashboard loads and renders correctly when accessed manually in Chrome.
The user is authenticated in Chrome/Google when CoWork attempts the browse.
CoWork gracefully falls back to pulling data from connected MCP servers (GA4, Google Ads, Meta, GSC), but the Looker Studio-specific calculated fields and blended data are missing from the output.
The error specifically mentions "Chrome tool parameter types" — this suggests the issue may be in how CoWork constructs the tool call to the browser/computer-use system, rather than a problem with the target page itself.