@omniaibot/win-x64 1.1.2 → 1.1.6

package/bin/omnibot-windows-x64/omnibot/references/runtime-and-status.md

@@ -0,0 +1,111 @@
+# Runtime and Status
+
+Use this file before troubleshooting. Runtime checks establish whether the daemon, extension, browser, visibility mode, license, and packaged skills are healthy.
+
+## Startup Check
+
+Run this sequence before diagnosing browser failures:
+
+```bash
+omnibot doctor
+omnibot status
+omnibot tabs
+omnibot visibility status
+omnibot browser current
+omnibot license status
+```
+
+Interpretation:
+
+- `doctor` checks daemon and extension health.
+- `status` checks daemon status only (lighter than `doctor`).
+- `tabs` proves connected tabs are visible and provides tab ids.
+- `visibility status` shows whether automation is visible, background, dedicated-profile, or headless.
+- `browser current` shows current browser runtime ownership.
+- `license status` verifies license state.
+
+If the extension is not connected, open Chrome or Edge with the omnibot extension loaded and keep an HTTP/HTTPS page open.
+
+## Daemon Lifecycle
+
+Top-level shortcuts:
+
+```bash
+omnibot status   # Show daemon status
+omnibot start    # Start the daemon
+omnibot stop     # Stop the daemon
+omnibot run      # Run daemon in foreground
+```
+
+Full form (also supported):
+
+```bash
+omnibot daemon run
+omnibot daemon start
+omnibot daemon stop
+omnibot daemon status
+```
+
+## doctor
+
+```bash
+omnibot doctor
+```
+
+Use `doctor` first when commands fail, tabs are empty, screenshots fail, or the agent cannot reach the browser.
+
+## tabs
+
+```bash
+omnibot tabs
+```
+
+Use `tabs` to discover tab ids. Save the target tab id and use it on every page-state command:
+
+```bash
+OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
+```
+
+## browser list/current
+
+```bash
+omnibot browser list
+omnibot browser current
+```
+
+Use browser status when multiple browser runtimes or agents may be active.
+
+## visibility status
+
+```bash
+omnibot visibility status
+```
+
+Use visibility status to confirm whether automation should share the user's visible browser state. Headless and dedicated-profile modes do not automatically inherit user login.
+
+## license status
+
+```bash
+omnibot license status
+```
+
+Use license status when runtime checks pass but features appear unavailable.
+
+## skills path
+
+```bash
+omnibot skills path
+```
+
+Use skills path to locate packaged skills for installation or inspection.
+
+## Skills Install
+
+```bash
+omnibot skills install --agent hermes --profile nuwa
+omnibot skills install --agent opencode
+omnibot skills install --agent claude
+omnibot skills install --agent codex
+```
+
+Install only when setting up or repairing an agent integration. It is not part of normal page operations.

package/bin/omnibot-windows-x64/omnibot/references/session-and-tabs.md

@@ -0,0 +1,164 @@
+# Sessions and Tabs
+
+Sessions and tabs are core reliability concepts, not advanced usage.
+
+## Session First
+
+`OMNIBOT_SESSION_TOKEN` is mandatory for every workflow.
+
+```bash
+OMNIBOT_SESSION_TOKEN=research omnibot tabs
+OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
+```
+
+The same token keeps one workflow isolated. Different tokens prevent independent agents from sharing default state.
+
+## Tab Explicit
+
+`--tab-id <TAB_ID>` is mandatory for every page-state command.
+
+```bash
+OMNIBOT_SESSION_TOKEN=checkout omnibot get url --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=checkout omnibot click --tab-id <TAB_ID> @e4
+OMNIBOT_SESSION_TOKEN=checkout omnibot get url --tab-id <TAB_ID>
+```
+
+Do not rely on default tab, active tab, current tab, or previous targeting state.
+
+## Explicit Targeting Model
+
+Page-state commands never infer a target tab. Always pass `--tab-id <TAB_ID>` for commands that read or mutate page state.
+
+Transport selection is internal. Omnibot may use any connected extension WebSocket to deliver extension-level commands, but that transport tab is never the page target.
+
+Do not use the first returned tab, `tabs[0]`, browser active tab, newest tab, or prior command state as a target.
+
+## Transport Is Not Target
+
+Omnibot can send extension commands through any connected extension WebSocket tab. That transport tab is not the page target. The target is only the tab id passed in the command, for example `--tab-id edge-client:123`.
+
+Safe sequence:
+
+```bash
+OMNIBOT_SESSION_TOKEN=research omnibot navigate https://example.com
+OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id edge-client:123
+OMNIBOT_SESSION_TOKEN=research omnibot click --tab-id edge-client:123 @e4
+OMNIBOT_SESSION_TOKEN=research omnibot wait --text "Saved" --tab-id edge-client:123
+```
+
+Unsafe sequence:
+
+```bash
+OMNIBOT_SESSION_TOKEN=research omnibot tabs
+OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i
+```
+
+The unsafe sequence has no target. Do not infer target from first tab, active tab, or prior operation.
+
+## Safe Browser Test Cleanup
+
+Browser integration tests must only close tabs they created:
+
+1. Record the list of existing tabs before creating fixtures.
+2. Create a unique fixture tab per case.
+3. Store the returned full tab id.
+4. Pass that id to every page-state command.
+5. Close only stored fixture ids in cleanup.
+6. Verify user tabs remain present after the test.
+
+## Why Both
+
+- Session = workflow isolation.
+- Tab ID = page targeting.
+
+Session alone does not prove which page receives a command. Tab ID alone does not isolate concurrent agents. Use both.
+
+## Ref Scope
+
+`@eN` refs are tab-scoped.
+
+Never reuse `@eN` across tabs. Never assume a ref remains valid after navigation, reload, major DOM changes, or a different snapshot.
+
+```bash
+OMNIBOT_SESSION_TOKEN=checkout omnibot snapshot -i --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=checkout omnibot click --tab-id <TAB_ID> @e4
+OMNIBOT_SESSION_TOKEN=checkout omnibot snapshot -i --tab-id <TAB_ID>
+```
+
+## Multi-Agent Pattern
+
+Agent A:
+
+```bash
+OMNIBOT_SESSION_TOKEN=research
+```
+
+Agent B:
+
+```bash
+OMNIBOT_SESSION_TOKEN=checkout
+```
+
+Agent C:
+
+```bash
+OMNIBOT_SESSION_TOKEN=debug
+```
+
+Each agent must:
+
+1. Set a stable token.
+2. Discover or create a tab.
+3. Save the tab id.
+4. Pass `--tab-id <TAB_ID>` on every page-state command.
+5. Run `snapshot` -> action -> verify, or `get/is` -> action -> `get/is`.
+
+Example:
+
+```bash
+OMNIBOT_SESSION_TOKEN=research omnibot tab new https://example.com --label research
+OMNIBOT_SESSION_TOKEN=research omnibot get url --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
+```
+
+## No Implicit Targeting
+
+Omnibot does not provide a workflow-level current tab command. Every command that reads or changes page state must receive `--tab-id <TAB_ID>` in that command invocation.
+
+This prevents stale target state and cross-agent tab confusion.
+
+## browser claim/release
+
+Use `browser claim` and `browser release` in multi-browser or multi-runtime scenarios where an agent must explicitly own or release a browser tab.
+
+```bash
+OMNIBOT_SESSION_TOKEN=research omnibot browser list
+OMNIBOT_SESSION_TOKEN=research omnibot browser current
+OMNIBOT_SESSION_TOKEN=research omnibot browser claim 123
+OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id 123
+OMNIBOT_SESSION_TOKEN=research omnibot browser release 123
+```
+
+Claiming does not replace `--tab-id`. It only documents or coordinates ownership.
+
+## visibility
+
+Visibility controls where automation runs:
+
+- `visible`: controls the user's already-open real browser tabs and preserves visible session state.
+- `background`: avoids foregrounding tabs unless requested.
+- `dedicated-profile`: launches or uses a separate profile.
+- `headless`: uses a headless browser context.
+- `launch`: starts a dedicated-profile or headless browser with an explicit user data dir.
+
+Examples:
+
+```bash
+omnibot visibility status
+omnibot visibility set visible
+omnibot visibility set background
+omnibot visibility set headless --user-data-dir /tmp/omnibot-headless
+omnibot visibility launch headless --user-data-dir /tmp/omnibot-headless
+```
+
+Headless and dedicated-profile modes do not automatically share the user's current tabs or login state. Verify login state before assuming access.

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/SKILL.md

@@ -12,7 +12,7 @@ metadata:
 
 Omnibot is Browser Infrastructure for AI Agents.
 
-It connects Hermes, Claude Code, Codex, OpenCode, MCP Agent Runtime, and other agent systems to a real Chromium browser through the local omnibot daemon and CLI.
+It connects Hermes, Claude Code, Codex, OpenCode, and other agent systems to a real Chromium browser through the local omnibot daemon and CLI.
 
 This skill is an execution specification for agents. It is not a human command manual.
 
@@ -108,18 +108,18 @@ Start from the task, not the command name. Use operation patterns for read, clic
 
 Use fallback tiers only after standard patterns fail. Collect evidence separately from fallback execution. The command reference is only a lookup table; it must not decide behavior.
 
-## Read vs Scan Routing
+## Read vs Snapshot Routing
 
 Choose by intent before choosing by command name:
 
 | Intent | Prefer | Why |
 | --- | --- | --- |
 | Summarize or extract page content, article text, search results, feeds, or long/lazy pages | `read` | Returns clean text/Markdown for agent reasoning. |
-| Quickly observe the current viewport before deciding what to do next | `scan --json` | Returns structured viewport state useful for routing. |
+| Quickly observe current visible UI structure before deciding what to do next | `snapshot -i` | Returns actionable refs and page structure for routing. |
 | Find buttons, links, inputs, or refs for a later action | `find` or `snapshot -i` | Produces actionable targets; `read` does not. |
 | Verify one concrete condition | `get`, `is`, or `wait` | Narrow evidence is more reliable than dumping a page. |
 
-Do not use `scan` as a long-form reader. Do not use `read` as the first step for click/fill workflows unless the user explicitly asked for page content first.
+Do not use `read` as the first step for click/fill workflows unless the user explicitly asked for page content first.
 
 ## Quick Routing
 

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/anti-patterns.md

@@ -4,7 +4,7 @@
 | --- | --- | --- |
 | Missing `OMNIBOT_SESSION_TOKEN` | Workflows can share implicit state across agents. | `OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>` |
 | Missing `--tab-id` | The command may target the wrong page. | Pass `--tab-id <TAB_ID>` on every page-state command. |
-| `execute-js` first | JavaScript bypasses standard browser interaction and hides better evidence. | Try semantic find, snapshot refs, selectors, DOM, and mouse first. |
+| `execute-js` first | JavaScript bypasses standard browser interaction and hides better evidence. | Try semantic find, snapshot refs, selectors, DOM, and mouse first. For CSS-only dropdowns, use JavaScript only after the trigger clicked, options remain absent from `snapshot -i`, and higher tiers cannot complete open-then-select. |
 | Reusing `@eN` across tabs | Refs are tab-scoped and may point to a different element elsewhere. | Take a fresh `snapshot -i --tab-id <TAB_ID>` per tab. |
 | Relying on implicit tab targeting | It is unavailable and unsafe for concurrent workflows. | Use explicit `--tab-id` on every page-state command. |
 | Using sleep instead of wait | Fixed sleeps are flaky and either too short or too slow. | Use `omnibot wait --text`, `--url`, selector state, load state, or `--fn`. |
@@ -12,7 +12,6 @@
 | Claiming success without evidence | The browser may not have changed as expected. | Cite verified URL, text, element state, screenshot, console, or network evidence. |
 | Raw CSS before semantic find | CSS is more brittle and less tied to user intent. | Start with `find role/text/label/placeholder/testid`. |
 | Screenshot when text extraction is enough | Screenshots cost more and are harder to parse. | Use `read` for page content or `get text` for a selector. |
-| Using `scan` for long-form reading | `scan` is viewport observation and may miss long/lazy content. | Use `read --screens N --tab-id <TAB_ID>`. |
 | Using `read` before an action workflow | `read` returns text, not stable action targets. | Use `find`, `snapshot -i`, `get`, or `is` for click/fill/verify workflows. |
 | Headless expecting existing user login | Headless does not automatically share the user's visible browser session. | Use visible/background mode for existing login or explicitly log in headless. |
 | Mixing multiple workflows in one session token | Agents can overwrite each other's default state. | Use different tokens: `research`, `checkout`, `debug`. |
@@ -31,5 +30,8 @@
 - "The ref probably still points to the same element."
 - "A screenshot is enough even though I need text."
 - "Sleep should be fine."
+- "The trigger clicked, so another `find text` should eventually select the option."
+- "`snapshot -i` cannot see the option, so the element must not exist."
+- "This dropdown is custom, so I can start with JavaScript."
 
 All of these mean: stop, re-enter the standard pattern, and make state explicit.

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/command-reference.md

@@ -80,30 +80,19 @@ Fallback relation: Not a fallback command.
 
 ## Reading
 
-### scan
-
-Purpose: Observe the current rendered viewport, especially before choosing a follow-up action.
-
-```bash
-OMNIBOT_SESSION_TOKEN=research omnibot scan --json --tab-id <TAB_ID>
-OMNIBOT_SESSION_TOKEN=research omnibot scan --text-only --tab-id <TAB_ID>
-```
-
-Preferred pattern: See `operation-patterns.md#read` and `operation-patterns.md#extraction`.
-Fallback relation: Use before `dom visible` or `execute-js` when structured viewport state is needed. Use `read` instead for long-form page text.
-
 ### read
 
 Purpose: Read clean rendered page text/Markdown from an existing tab or a temporary URL tab.
 
 ```bash
 OMNIBOT_SESSION_TOKEN=research omnibot read --screens 5 --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=research omnibot read --screens 5 --timeout 120 --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot read --screens 3 https://example.com/article
 OMNIBOT_SESSION_TOKEN=research omnibot read --json --screens 5 --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `operation-patterns.md#read` and `operation-patterns.md#extraction`.
-Fallback relation: Prefer for page content. Use `scan --json` when the next step is action planning, and `snapshot -i` when actionable refs are needed.
+Fallback relation: Prefer for page content. Use `snapshot -i` when the next step is action planning, and `get`/`is`/`wait` for narrow state verification.
 
 ### snapshot -i
 
@@ -241,7 +230,7 @@ OMNIBOT_SESSION_TOKEN=form omnibot select @e5 "US" --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `operation-patterns.md#select--check`.
-Fallback relation: Prefer refs/selectors before JavaScript value changes.
+Fallback relation: Prefer refs/selectors before JavaScript value changes. For CSS-only dropdowns whose options are absent from `snapshot -i`, see `fallback-operations.md#css-only-dropdown-javascript-fallback`.
 
 ### check / uncheck
 
@@ -350,7 +339,7 @@ OMNIBOT_SESSION_TOKEN=repair omnibot execute-js --file /tmp/repair.js --tab-id <
 ```
 
 Preferred pattern: See `fallback-operations.md#javascript-fallback`.
-Fallback relation: After semantic, refs, selector, DOM, and mouse are insufficient.
+Fallback relation: After semantic, refs, selector, DOM, and mouse are insufficient. Valid examples include CSS-only dropdowns where the trigger exists but option refs are absent from `snapshot -i`.
 
 ### cdp
 
@@ -443,7 +432,7 @@ Fallback relation: Prefer over shell sleep.
 Purpose: Send short command arrays as JSON or from a file.
 
 ```bash
-OMNIBOT_SESSION_TOKEN=research omnibot batch '[{"cmd":"scan"},{"cmd":"snapshot","interactive":true}]' --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=research omnibot batch '[{"cmd":"snapshot","interactive":true}]' --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot batch --file /tmp/omnibot-batch.json --tab-id <TAB_ID>
 ```
 

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/debugging-and-evidence.md

@@ -89,7 +89,7 @@ CDP inspection is not a first-choice operation path. If CDP changes state, it be
 Before reporting a browser issue, collect the smallest evidence set that explains it:
 
 - Runtime: `doctor`, `tabs`, `visibility status`.
-- Page state: `get`, `is`, `scan`, or `snapshot`.
+- Page state: `get`, `is`, `snapshot`, or `wait`.
 - Visual proof: `screenshot --annotate` only if visual state matters.
 - Browser diagnostics: `console errors` and `network summary`.
 - Reproduction artifact: `trace` or `record` when the flow is unstable.

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/fallback-operations.md

@@ -106,7 +106,8 @@ Use `execute-js` only when:
 - CSS selector operation fails.
 - DOM fallback fails.
 - A complex frontend event must be triggered.
-- Runtime state cannot be read through `read`, `scan`, `get`, or `is`.
+- A CSS-only dropdown or hover menu requires an atomic open-then-select sequence, and `snapshot -i` confirms the option nodes are absent from the accessibility tree.
+- Runtime state cannot be read through `read`, `snapshot`, `get`, or `is`.
 
 Read-only JavaScript fallback:
 
@@ -129,6 +130,64 @@ OMNIBOT_SESSION_TOKEN=repair omnibot execute-js "document.querySelector('button[
 OMNIBOT_SESSION_TOKEN=repair omnibot wait --url "/dashboard" --tab-id <TAB_ID>
 ```
 
+### CSS-only dropdown JavaScript fallback
+
+Use this only after the trigger is known and higher tiers failed: semantic `find` clicked the trigger or found the text, `snapshot -i` could not expose option refs, selector/DOM/mouse could not complete the two-step interaction, and verification showed the selection did not change.
+
+Example for a visible trigger like `按留言时间排序` and a target option text:
+
+```bash
+OMNIBOT_SESSION_TOKEN=repair omnibot execute-js --file /tmp/omnibot-css-dropdown.js --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=repair omnibot snapshot -i --tab-id <TAB_ID>
+```
+
+`/tmp/omnibot-css-dropdown.js`:
+
+```js
+const triggerText = '按留言时间排序';
+const optionText = '目标选项文本';
+
+const visibleElements = [...document.querySelectorAll('button, [role="button"], [aria-haspopup], div, span, li')]
+  .filter((el) => {
+    const style = getComputedStyle(el);
+    const box = el.getBoundingClientRect();
+    return style.display !== 'none' && style.visibility !== 'hidden' && box.width > 0 && box.height > 0;
+  });
+
+const byExactText = (text) => visibleElements.find((el) => el.textContent?.trim() === text);
+const trigger = byExactText(triggerText);
+if (!trigger) {
+  return { ok: false, reason: 'trigger-not-found', triggerText, optionText };
+}
+
+trigger.click();
+await new Promise((resolve) => requestAnimationFrame(() => requestAnimationFrame(resolve)));
+
+const option = [...document.querySelectorAll('div, span, li, button, [role="option"], [role="menuitem"]')]
+  .filter((el) => {
+    const style = getComputedStyle(el);
+    const box = el.getBoundingClientRect();
+    return style.display !== 'none' && style.visibility !== 'hidden' && box.width > 0 && box.height > 0;
+  })
+  .find((el) => el.textContent?.trim() === optionText);
+
+if (!option) {
+  return { ok: false, reason: 'option-not-found-after-trigger-click', triggerText, optionText };
+}
+
+option.click();
+await new Promise((resolve) => requestAnimationFrame(() => requestAnimationFrame(resolve)));
+
+return {
+  ok: true,
+  triggerText,
+  optionText,
+  selectedText: trigger.textContent?.trim(),
+};
+```
+
+Verify with the user-visible result, not just `{ ok: true }`: selected label, sorted result order, result count, URL/query state, or another page-specific condition.
+
 Prefer `--file` for longer scripts:
 
 ```bash

package/bin/omnibot-windows-x64/omnibot/skills/omnibot/references/operation-patterns.md

@@ -8,7 +8,7 @@ Use this file to choose behavior by task. Every page-state workflow must set `OM
 
 Use Read when the agent needs clean rendered page content: article text, search results, feed items, long pages, lazy-loaded text, or a human-readable summary source.
 
-Use targeted state commands when the agent needs one value, visibility, enabled/checked state, layout box, or computed styles. Use scan when the agent needs a structured current-viewport observation for deciding the next action.
+Use targeted state commands when the agent needs one value, visibility, enabled/checked state, layout box, or computed styles. Use `snapshot -i` when the agent needs current visible UI structure for deciding the next action.
 
 ### Preferred sequence
 
@@ -17,9 +17,8 @@ Use targeted state commands when the agent needs one value, visibility, enabled/
 3. `read <URL>` when opening a temporary tab only for reading that URL.
 4. `get title/url/text/html/value/attr/count/box/styles` for narrow evidence.
 5. `is visible/enabled/checked` for boolean state.
-6. `scan --json` only when the next step depends on current viewport structure.
-7. `snapshot -i` when actionable refs are needed.
-8. `dom visible` or `execute-js` fallback only after standard reads cannot access the state.
+5. `snapshot -i` when actionable refs are needed.
+6. `dom visible` or `execute-js` fallback only after standard reads cannot access the state.
 
 ### Example
 
@@ -40,7 +39,7 @@ OMNIBOT_SESSION_TOKEN=research omnibot get count ".result" --tab-id <TAB_ID>
 
 ### Fallback entry point
 
-If `read`, targeted reads, or scan omit needed runtime state, go to `fallback-operations.md#fallback-tier-model`. Start with DOM fallback before JavaScript.
+If `read` or targeted reads omit needed runtime state, go to `fallback-operations.md#fallback-tier-model`. Start with DOM fallback before JavaScript.
 
 ## Click
 
@@ -161,9 +160,23 @@ OMNIBOT_SESSION_TOKEN=form omnibot is checked "#agree" --tab-id <TAB_ID>
 
 For checkboxes, verify boolean state. For selects, verify value or dependent page state.
 
+### CSS-only dropdowns and custom menus
+
+Some dropdowns, hover menus, tooltips, and custom selects are CSS-only widgets. The visible trigger may be accessible, while the option nodes are hidden `<div>` elements without `role`, accessible name, or stable refs.
+
+Use this evidence path before JavaScript:
+
+1. Try semantic `find` or a normal `select`/`click` against the trigger.
+2. Verify whether the selected label, result order, or dependent state changed.
+3. Run `snapshot -i` after opening the control.
+4. If the trigger clicked but options are absent from the accessibility tree, do not keep retrying `find` or stale refs.
+5. Escalate to `fallback-operations.md#css-only-dropdown-javascript-fallback` for an atomic open-then-select script.
+
+`snapshot -i` not showing an option does not prove the DOM node is missing. It may only prove the widget is not exposed through the accessibility tree.
+
 ### Fallback entry point
 
-If native select/check fails, use `fallback-operations.md#selector-fallback`, then JavaScript only if events must be synthesized.
+If native select/check fails, use `fallback-operations.md#selector-fallback`. Use JavaScript only if events must be synthesized or if evidence shows a CSS-only multi-step widget cannot be completed through semantic, snapshot, selector, DOM, or mouse tiers.
 
 ## Navigation
 
@@ -261,7 +274,7 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot wait --fn "window.appReady === true" --ta
 
 ### Verification
 
-After waiting, read the final condition with `get`, `is`, `scan`, or `snapshot`.
+After waiting, read the final condition with `get`, `is`, `wait`, or `snapshot`.
 
 ### Fallback entry point
 
@@ -277,7 +290,7 @@ Use Extraction for retrieving page text, HTML fragments, links, counts, assets,
 
 1. `get text/html/attr/count` for targeted extraction.
 2. `read --screens N` for clean page text, long pages, or lazy-loaded content.
-3. `scan --json` for structured viewport extraction before action planning.
+3. `snapshot -i` for structured page observation before action planning.
 4. `assets list/export` for resources.
 5. `clipboard read` only when clipboard content is part of the task.
 
@@ -302,7 +315,7 @@ Verify extraction completeness with expected markers in `read`, element counts,
 
 ### Fallback entry point
 
-If content exists only in runtime objects, use `fallback-operations.md#javascript-fallback` after explaining why `read`, `scan`, and `get` could not access it.
+If content exists only in runtime objects, use `fallback-operations.md#javascript-fallback` after explaining why `read`, `snapshot`, and `get` could not access it.
 
 ## Upload
 
@@ -352,7 +365,7 @@ Use Batch for short, known-safe command chains where the target tab and verifica
 ### Example
 
 ```bash
-OMNIBOT_SESSION_TOKEN=research omnibot batch '[{"cmd":"scan"},{"cmd":"snapshot","interactive":true}]' --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=research omnibot batch '[{"cmd":"snapshot","interactive":true}]' --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=research omnibot snapshot -i --tab-id <TAB_ID>
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omniaibot/win-x64",
-  "version": "1.1.2",
+  "version": "1.1.6",
   "description": "omnibot executable for Windows x64",
   "os": [
     "win32"
@@ -15,9 +15,9 @@
     "bin/"
   ],
   "keywords": [
-    "mcp",
     "browser",
     "automation",
+    "agent",
     "omnibot"
   ],
   "author": "Unagi-cq",