For post-run inspection, own the browser lifetime with an agent session or an explicitly created browser. A one-shot agent.run(...) closes an implicitly created browser when the run completes.
Use the share button in the Debug UI timeline, or press Ctrl+Shift+S / Cmd+Shift+S, when another person or agent needs the exact browser state you are looking at. In live mode, the share sheet captures the current live position. In replay mode, it captures the scrubbed timestamp and can include playback speed.Use the share link for trusted humans who need to open the same browser moment. Use Copy as Markdown or Copy as JSON when an agent, support workflow, or internal tool needs the context without receiving a screen share.The agent context can include the recording segment, timestamp, sanitized Debug UI URL, page URL, browser status, readiness, active page, control lease state, nearby events, console errors, and network failures when those signals are available.Good uses for browser moments:
Hand a reviewer the exact page state behind an approval or blocker.
Give an agent the current URL, timestamp, and nearby diagnostic signals before asking it to reason about the run.
Attach a specific browser moment to a support ticket, incident note, or job review.
Browser-moment links inherit the Debug UI capability. Share them only with people or systems that should inspect that browser session. Markdown and JSON context can also contain sensitive page evidence.