browser

# Browser One library, two engines. omowright ships inside this skill; choose the engine before you act: | You need | Engine | Entry point | |---|---|---| | A site the user is signed into, their open tabs, a form, a click-through, a screenshot, web QA, an extension popup | **attached** — the user's own browser through BrowserSkill | `connectBrowserSkill()` | | A throwaway profile, bot-scoring evasion, a CAPTCHA, network interception, a QA flight trace, coordinate control, headless runs | **owned** — a browser your code launches | `connectPipe()` / `connectCloakProfile()` — [references/owned-engine/README.md](references/owned-engine/README.md) | | Text out of a URL, a 403 bypass, a platform that blocks fetchers | neither | the `ultimate-browsing` skill | **Attached is the default,** because it is the only engine carrying the user's logins and the only one where a human is a single call away. Never substitute one engine for the other silently: if the attached engine is not set up, run the onboarding script and tell the user its one remaining step. ## Step 0 — load omowright and prove the stack ```js const { loadOmowright } = await import("<skill-root>/scripts/omowright.mjs") const { omowright } = await loadOmowright() // { connectBrowserSkill, bskSnapshot, connectPipe, ... } ``` ```bash node "<skill-root>/scripts/browser-doctor.mjs" --json ``` | State | Meaning | Next | |---|---|---| | `ready` | CLI, daemon and a connected browser | start a session | | `no-cli` ...