Confirmed tool-description mismatch
Reviewed Odin at 886c36d8ebe861aa987059a1744d45b78797baae (v4.7.0). Suggested priority: P3 documentation/behavioral guidance.
browser_click tells the model to follow up with browser_read_page to inspect content after clicking. But each browser operation uses a fresh isolated context. A follow-up reload cannot inspect transient state from the previous click.
Real-browser reproduction
A fixture button sets a cookie/localStorage item and navigates to /dashboard. The click tool reports Dashboard and the server sees the cookie on that navigation. The following browser_read_page on /dashboard returns:
cookie=false local=missing
Independently reproduced with actual headless Chromium against a disposable loopback fixture. This is distinct from redirect issue #374: cross-call isolation persists even after redirect handling is corrected.
Acceptance criteria
- Tool descriptions explicitly state that subsequent calls reload in new contexts and do not retain cookies, storage, form or DOM state from a previous call.
- Limit click-then-read advice to independently reloadable resulting resources, not an assertion that it reads the clicked page instance.
- Describe available same-call observation techniques accurately, without suggesting blind duplicate submissions.
- Keep current isolation unchanged. Persistent browser sessions would be a separate feature and authorization design, not a documentation fix.
- Update generated tool reference and relevant description tests together.
Behavior change: prompt guidance becomes truthful; no browser permission/session behavior changes. No code was changed.
Confirmed tool-description mismatch
Reviewed Odin at
886c36d8ebe861aa987059a1744d45b78797baae(v4.7.0). Suggested priority: P3 documentation/behavioral guidance.browser_clicktells the model to follow up withbrowser_read_pageto inspect content after clicking. But each browser operation uses a fresh isolated context. A follow-up reload cannot inspect transient state from the previous click.Real-browser reproduction
A fixture button sets a cookie/localStorage item and navigates to
/dashboard. The click tool reports Dashboard and the server sees the cookie on that navigation. The followingbrowser_read_pageon/dashboardreturns:Independently reproduced with actual headless Chromium against a disposable loopback fixture. This is distinct from redirect issue #374: cross-call isolation persists even after redirect handling is corrected.
Acceptance criteria
Behavior change: prompt guidance becomes truthful; no browser permission/session behavior changes. No code was changed.