lazycodex-ai 5.0.0-beta.85 → 5.0.0-beta.87

package/packages/shared-skills/skills/browser/references/recipes/1password.md

@@ -16,25 +16,27 @@ not in a cookie. So:
 Therefore: borrow the existing tab, read, return it. Do not open, do not navigate away, do not
 "refresh to fix" anything.
 
-```bash
-bsk tab list --scope user           # find the already-signed-in tab
-bsk tab borrow <tab-id>
-# ... read ...
-bsk tab return <tab-id>
+```js
+const { tabs } = await session.tabList({ scope: "user" })          // find the already-signed-in tab by URL
+const vault = tabs.find((t) => /my\.1password\.com\/(?:vaults|app)/.test(t.url))
+await session.tabBorrow(vault.tab_id)                               // the user confirms
+// ... read ...
+await session.tabReturn(vault.tab_id)
 ```
 
 ## Check liveness by URL, never by title
 
 The app mutates its URL hash without updating the document title, so a signed-in vault can still
 report a sign-in title. A live session's `location.href` contains the app path and never the
-sign-in path. Read the URL.
+sign-in path. Read the URL from `tabList`, or `session.evaluate("location.href")`.
 
 ## The browser may be shared
 
 Other automation may be driving the same window.
 
-- **Clear the search box before typing.** It often holds someone else's query, and typing alone
-  appends to it, returning confident results for the wrong search.
+- **Clear the search box before typing** (`fill(target, value, { clearBefore: true })`). It often
+  holds someone else's query, and typing alone appends to it, returning confident results for the
+  wrong search.
 - **Read the autocomplete listbox, not the results grid.** The grid holds whatever query was last
   committed, possibly by another actor. Scraping every option on the page silently merges two
   different searches.
@@ -42,11 +44,11 @@ Other automation may be driving the same window.
 
 ## If it is locked
 
-```bash
-bsk request-help --session <id> --prompt "Please unlock 1Password in this tab, then continue."
+```js
+await session.requestHelp({ prompt: "Please unlock 1Password in this tab, then continue." })
 ```
 
-Then observe again.
+Then read the page again.
 
 ## Not in scope
 

package/packages/shared-skills/skills/browser/references/remote.md

@@ -6,18 +6,19 @@ nothing in this package needs to bridge it.
 Shape:
 
 - The **browser machine** needs only the extension.
-- The **agent machine** runs the `bsk` CLI and this skill.
+- The **agent machine** runs the `bsk` daemon, omowright and this skill.
 - They are joined by a daemon in server mode plus a pairing link.
 
 ```bash
-bsk daemon start --mode server      # on the machine the agent runs on
+bsk daemon start --mode server      # on the machine the agent runs on; WSS is required off loopback
 ```
 
 Then follow upstream's pairing guide, which owns the current flag surface and the TLS
 prerequisites: https://github.com/Tencent/BrowserSkill/blob/main/docs/remote-extension-connection.md
 
-Once paired, every command in `commands.md` behaves identically; `--out` paths still resolve on
-the machine that ran the command.
+Once paired, `connectBrowserSkill()` and every session method behave identically; screenshot
+buffers arrive on the machine that ran the call. Windows named pipes are not discovered
+automatically — pass `sockPath` to `connectBrowserSkill()`.
 
 If pairing is not configured, say so and ask. Do not substitute a browser on the agent machine:
 the point of the attached engine is the sessions that live in the user's browser, and a local