Docs

Use browser-session automation

Use scoped browser-session automation to inspect UI and verify docs.

What browser-session automation is for

Browser-session automation lets Codex and other agents safely operate a restricted set of actions in the exact browser session that asked for help. It is useful for opening panels, checking visible UI, reading state, and validating that docs match the product.

Use the browser session

  1. Follow Test browser workflows with the CLI to authenticate for the intended site and resolve the browser and project.
  2. Read that session's API declaration and inspect its page before acting.
  3. Use high-level actions such as docs actions before falling back to generic browser exec scripts.
  4. Use assertions such as waiting for text or a URL when verifying behavior.

For local source development only, load the matching development environment. For a local hub, refresh it with cd src && eval "$(pnpm -s dev:hub:env)" before live browser commands.

Keep automation scoped

Prefer typed actions and restricted QuickJS browser exec APIs over raw DOM scripts. The goal is enough UI access for useful help and verification, not an unbounded remote-control surface.

Why this matters in CoCalc

The same infrastructure that lets Codex open a Secrets modal can also verify that docs are still true after frontend changes. This makes documentation, support, and agent behavior part of one testable system.