Make next-dev-loop browser headless by default (#98318)
## Summary - make `next-dev-loop` open `agent-browser` headlessly for routine verification - keep one worktree-scoped restored `agent-browser` session - open the current URL in the coding harness's inline browser when the user asks to see the UI, while making clear that it is a separate browser context - relaunch the same `agent-browser` session with `--headed` only when login or existing browser state must carry over - update Cache Components adoption guidance to use the same explicit browser handoff choices ## Why Runtime browser verification is still needed for rendered behavior, navigation, browser errors, and React state that compilation and type checking cannot prove. That verification does not need to open a visible browser for every task. The coding harness may not be able to embed an existing `agent-browser` session. The instructions now distinguish an inline presentation handoff, which has separate cookies and storage, from a headed `agent-browser` handoff that preserves the restored session's state. ## Verification - Prettier passed for `skills/next-dev-loop/SKILL.md` and `skills/next-cache-components-adoption/SKILL.md` - verified the headless `agent-browser` flow and a separate coding-harness inline-browser handoff against a running Next.js app - not run: test suite (skill instructions only) <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment