← Back to Browser
OpenClaw browser

State, cookies, storage, and emulation

Use this page when browser behavior changes with viewport, device, cookies, locale, timezone, or stored state.

Core idea A lot of “random” page behavior is really state you can inspect or change on purpose.
State model

Browser state is part of the workflow

OpenClaw can change viewport, named devices, offline mode, theme, locale, timezone, geolocation, cookies, and storage deliberately.

That makes state inspection and state control part of strong browser workflows, not side trivia.

Testing lanes

Use the right kind of state change

Layout lane

Viewport and device controls

Reproduce breakpoint and device-specific rendering issues.

Environment lane

Locale, timezone, geo, and offline mode

Reproduce content and behavior changes that only appear under certain conditions.

Session lane

Cookies and storage

Explain logged-in, logged-out, flagged, or personalized behavior.

Reset caution

Reset state carefully

  • inspect cookies and storage before clearing them
  • treat resets as intentional troubleshooting moves, not reflexes
  • verify visually or structurally after changing browser state
Next route

Read the right follow-on page