@omniaibot/win-x64 1.6.3 → 1.6.5

package/bin/omnibot-windows-x64/VERSION

@@ -1 +1 @@
-1.6.3
+1.6.5 

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

@@ -140,6 +140,18 @@ Do not use `read` as the first step for click/fill workflows unless the user exp
 
 Use `select @combobox "value"` for native selects or simple controls. Use `click @option` when `snapshot -i` exposes auto-probed combobox option refs. Do not manually reopen every dropdown just to discover options unless `snapshot -i` did not expose option refs.
 
+## Rich Text Article Editors
+
+ContentEditable rich text editors (ProseMirror, Quill, Draft.js, Slate, ByteDance/Toutiao article body, etc.) are often missing from the AX tree. `snapshot -i` appends them under `# DOM Rich Text Editors` as `@eN [richtext] "..." [contenteditable=true]` refs.
+
+- Detect the body editor: `snapshot -i` → look for `@eN [richtext]` under `# DOM Rich Text Editors`. Do not fill the article body through a `[textbox]` title ref.
+- Replace the whole body: `fill @richtext "paragraph 1\n\nparagraph 2"`. Empty lines split paragraphs; the previous content is cleared and `input`/`change` events are dispatched.
+- Append to the body: `type @richtext " additional text"`.
+- Focus before keyboard input: click `@richtext` first, then `press`/`keyboard`.
+- Raw selector fallback: `omnibot fill '[contenteditable="true"]' "..."` also routes through the rich text path when the selector looks like a rich editor.
+
+Do not use `execute-js` first for rich text writes; `fill`/`type` on the `[richtext]` ref is the supported path.
+
 ## Quick Routing
 
 | Need | Read |

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

@@ -28,6 +28,10 @@
 | Revealing sensitive network data | Cookies, auth headers, full addresses, phone numbers, and payment data must not be pasted into reports. | Report host, path, method, status, and non-sensitive payload shape only. |
 | Using stale `@eN` refs after a failed click | Refs may have expired or the page may have changed. | Re-observe with `snapshot -i` or use a higher-evidence fallback. |
 | `Network.enable` without log retrieval | Raw `cdp` calls are one-shot and do not persist events for later reading. | Use `network clear -> network start -> one action -> network stop -> network logs/summary`. |
+| Writing the article body into the title field | Rich text article body editors are often missing from the AX tree; filling the only visible `[textbox]` (title) overwrites the wrong control. | Run `snapshot -i`, find the body under `# DOM Rich Text Editors` as `@eN [richtext]`, then `fill @richtext "..."`. |
+| `execute-js` for rich text body before `fill @richtext` | ContentEditable writes need event dispatch and framework integration; ad-hoc `innerHTML` bypasses Omnibot's supported path. | Use `fill @richtext "p1\n\np2"` or `type @richtext " text"` first. |
+| Counting `<img>` nodes to detect duplicate images in a rich editor | ProseMirror/Toutiao image cards keep a hidden `<templ>` template and a visible `<mask>` copy of the same `<img>`, so `.ProseMirror img` returns 2 for one logical image and falsely reports duplication. | Count image card containers (`.ProseMirror [__syl_tag=true]` or `.ProseMirror .pgc-image`), one per inserted image. |
+| Inserting an image via `click @richtext` + `press End` | The caret stays on the first line; the image lands at the editor root instead of the target paragraph. | Use `find text "<anchor phrase>" --action click` to collapse the selection at the end of the matched phrase, then open the image tool and upload. |
 
 Do not manually reopen a dropdown just to discover options if `snapshot -i` already lists them.
 
@@ -45,5 +49,9 @@ Do not manually reopen a dropdown just to discover options if `snapshot -i` alre
 - "I remember the command syntax from before."
 - "`Network.enable` should be enough to capture requests."
 - "It is just a checkout preview, clicking pay should be fine."
+- "The article body is not in `snapshot -i`, so I will fill the title textbox."
+- "I will just set `innerHTML` on the contenteditable with `execute-js`."
+- "`.ProseMirror img` returned 2, so the image was inserted twice."
+- "I clicked the editor and pressed End, so the caret must be after the last paragraph."
 
 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

@@ -174,6 +174,8 @@ Fallback relation: Tier 2 with refs, Tier 3 with selector.
 
 Combobox option refs: if `snapshot -i` shows `@eN [option] "OpenAI Chat"`, prefer `click @eN` over JavaScript fallback. Omnibot will reopen the owning combobox when needed.
 
+Rich text editor refs: if `snapshot -i` shows `@eN [richtext] "..." [contenteditable=true]` under `# DOM Rich Text Editors`, treat it as the article body editor. Use `fill @richtext` to replace the whole body (supports `\n\n` for paragraphs) and `type @richtext` to append. Do not fall back to `execute-js` first.
+
 ### dblclick
 
 Purpose: Double-click an element by `@eN` ref or selector.
@@ -197,6 +199,14 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot fill "input[name=email]" "a@b.com" --tab-
 Preferred pattern: See `operation-patterns.md#fill`.
 Fallback relation: Tier 2 with refs, Tier 3 with selector.
 
+Rich text body editors (ProseMirror/Quill/Draft.js/Slate/Toutiao article body): if the target is an `@eN [richtext]` ref, `fill` writes through a dedicated contenteditable path that clears the previous body and dispatches `input`/`change` events. Split paragraphs with an empty line:
+
+```bash
+OMNIBOT_SESSION_TOKEN=editor omnibot fill --tab-id <TAB_ID> @eN "First paragraph.\n\nSecond paragraph."
+```
+
+Raw selector fallback is supported for selectors that look like a rich editor (e.g. `[contenteditable="true"]`, `.ProseMirror`, `.ql-editor`).
+
 ### type
 
 Purpose: Type text into an element.
@@ -208,6 +218,8 @@ OMNIBOT_SESSION_TOKEN=search omnibot type --tab-id <TAB_ID> @e3 "omnibot"
 Preferred pattern: See `operation-patterns.md#fill`.
 Fallback relation: Use after fill is not appropriate or focus is needed.
 
+For `@eN [richtext]` article body editors, `type` appends at the cursor position. Click the `@richtext` ref first to focus the editor.
+
 ### press
 
 Purpose: Press a key in the target tab.
@@ -290,14 +302,14 @@ Fallback relation: Mouse drag is Tier 5 if element drag fails.
 
 ### upload
 
-Purpose: Reserved command for local file upload. Native upload is currently unavailable in the extension transport.
+Purpose: Attach a local file to an `<input type="file">` element via CDP (`DOM.setFileInputFiles`), with nodeId and JS `DataTransfer` fallbacks.
 
 ```bash
-# Do not use in agent workflows until file chooser support is implemented.
+OMNIBOT_SESSION_TOKEN=form omnibot upload "input[type=file]" /path/to/file.png --tab-id <TAB_ID>
 ```
 
 Preferred pattern: See `operation-patterns.md#upload`.
-Fallback relation: Do not treat JavaScript as a normal upload fallback.
+Fallback relation: The CLI falls back from CDP objectId → CDP nodeId → JS DataTransfer. Do not stack additional JavaScript fallbacks.
 
 ### keyboard / keydown / keyup
 
@@ -326,6 +338,8 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot find testid submit-button --action click
 OMNIBOT_SESSION_TOKEN=checkout omnibot find nth ".card" 2 --action click --tab-id <TAB_ID>
 ```
 
+Text-node precision: `find text` walks the DOM text nodes and marks the nearest visible container of the matching text, not the first ancestor whose `textContent` happens to include the needle. The matched offset/length is stored on the element, so `--action click` positions the mouse at the end of the matched text. Inside a `contenteditable` body (ProseMirror/Quill/etc.), the selection is collapsed right after the matched text and the editor is focused, so a follow-up image insertion lands at the intended paragraph instead of the editor root.
+
 Preferred pattern: See `operation-patterns.md#click` and `operation-patterns.md#fill`.
 Fallback relation: Tier 1. Explain failure before using refs, selectors, DOM, mouse, JavaScript, or CDP.
 

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

@@ -109,6 +109,8 @@ Use `execute-js` only when:
 - 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`.
 
+Rich text article body editors (`@eN [richtext]`, `.ProseMirror`, `.ql-editor`, `[contenteditable="true"]`) have native `fill`/`type` support. Do not fall back to JavaScript for richtext writes; use `fill @richtext "..."` first.
+
 Read-only JavaScript fallback:
 
 ```bash

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

@@ -99,7 +99,7 @@ When `snapshot -i` shows only `StaticText` for a visible control label, do not a
 
 ### When to use
 
-Use Fill for text inputs, textareas, search boxes, login fields, and form fields where the final value must be controlled.
+Use Fill for text inputs, textareas, search boxes, login fields, form fields where the final value must be controlled, and rich text article body editors (contenteditable ProseMirror/Quill/Draft.js/Slate/Toutiao article body).
 
 ### Preferred sequence
 
@@ -124,6 +124,21 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot fill --tab-id <TAB_ID> @e2 "a@b.com"
 OMNIBOT_SESSION_TOKEN=checkout omnibot get value "input[name=email]" --tab-id <TAB_ID>
 ```
 
+### Rich text article body
+
+For article body editors exposed as `@eN [richtext] "..." [contenteditable=true]` under `# DOM Rich Text Editors`:
+
+```bash
+OMNIBOT_SESSION_TOKEN=editor omnibot snapshot -i --tab-id <TAB_ID>
+# Body appears under "# DOM Rich Text Editors": @eN [richtext] "..."
+OMNIBOT_SESSION_TOKEN=editor omnibot fill --tab-id <TAB_ID> @eN "First paragraph.\n\nSecond paragraph."
+OMNIBOT_SESSION_TOKEN=editor omnibot snapshot -i --tab-id <TAB_ID>  # verify body content replaced
+```
+
+- `\n\n` splits paragraphs; previous content is cleared.
+- `type @richtext " text"` appends at the cursor (click the ref first to focus).
+- Do NOT write the article body into a `[textbox]` title field. Title and richtext body are separate refs.
+
 ### Verification
 
 Use `get value`, visible validation text, enabled state, or submit readiness:
@@ -133,6 +148,24 @@ OMNIBOT_SESSION_TOKEN=checkout omnibot get value "input[name=email]" --tab-id <T
 OMNIBOT_SESSION_TOKEN=checkout omnibot is enabled "button[type=submit]" --tab-id <TAB_ID>
 ```
 
+For richtext bodies, re-run `snapshot -i` and confirm the `@eN [richtext]` name matches the intended content.
+
+### Cursor positioning and inline image insertion
+
+For `contenteditable` article bodies (ProseMirror/Quill/Draft.js/Slate/Toutiao article body), `find text "<anchor phrase>" --action click` collapses the editor selection at the end of the matched phrase and focuses the editor. Use this to place the caret at a specific paragraph before inserting an image, typing, or pressing keys. Do not rely on a bare `click` of the editor followed by `press End`, because the caret would stay on the first line.
+
+Insert an image after a specific paragraph:
+
+```bash
+OMNIBOT_SESSION_TOKEN=editor omnibot find text "第二段锚点文字" --action click --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=editor omnibot click ".syl-toolbar-tool.image .syl-toolbar-button" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=editor omnibot wait --selector ".upload-image-panel input[type=file]" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=editor omnibot upload ".upload-image-panel input[type=file]" "/path/to/image.png" --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=editor omnibot find role button --name "确定" --action click --tab-id <TAB_ID>
+```
+
+Verify the inserted image by counting visible image cards, not raw `<img>` nodes. Toutiao/ProseMirror image cards keep a hidden `<templ>` template and a visible `<mask>` copy of the same `<img>`, so `.ProseMirror img` returns 2 for one logical image. Count the image card container instead (e.g. `.ProseMirror [__syl_tag=true]` or `.ProseMirror .pgc-image`), which reports one per inserted image.
+
 ### Fallback entry point
 
 If fill does not update the application state, use `fallback-operations.md#javascript-fallback` only after selector/focus/type attempts fail. JavaScript must dispatch real `input` and `change` events.
@@ -333,32 +366,35 @@ If content exists only in runtime objects, use `fallback-operations.md#javascrip
 
 ### When to use
 
-Native upload is currently unavailable in the extension transport. Do not use `omnibot upload` as an agent workflow step until file chooser support is implemented.
+Use `omnibot upload` to attach a local file to an `<input type="file">` element. The command speaks CDP (`DOM.setFileInputFiles`) through the extension debugger transport, with a JS `DataTransfer` fallback for pages that reject programmatic file assignment.
 
 ### Preferred sequence
 
 1. Observe the upload UI and confirm the task requires a local file.
-2. Report that native upload is currently unavailable.
-3. If the user still wants a workaround, ask for approval before using page-specific JavaScript or manual browser interaction.
+2. Locate the file input via `snapshot -i` or a CSS selector.
+3. Run `omnibot upload <selector> <local-file> --tab-id <TAB_ID>`.
+4. Verify the file was accepted (filename, count, enabled submit state, or application-specific confirmation).
 
 ### Example
 
 ```bash
 OMNIBOT_SESSION_TOKEN=form omnibot snapshot -i --tab-id <TAB_ID>
-# upload is currently unavailable; do not run omnibot upload here.
+OMNIBOT_SESSION_TOKEN=form omnibot upload "input[type=file]" /path/to/cover.png --tab-id <TAB_ID>
+OMNIBOT_SESSION_TOKEN=form omnibot is enabled "button[type=submit]" --tab-id <TAB_ID>
 ```
 
 ### Verification
 
-If upload support is implemented later, verify with visible filename, count, enabled submit state, or application-specific confirmation:
+Confirm the input accepted the file:
 
 ```bash
+OMNIBOT_SESSION_TOKEN=form omnibot get "input[type=file]" attr value --tab-id <TAB_ID>
 OMNIBOT_SESSION_TOKEN=form omnibot is enabled "button[type=submit]" --tab-id <TAB_ID>
 ```
 
 ### Fallback entry point
 
-Do not treat JavaScript as a normal upload fallback. File inputs and browser file chooser behavior are security-sensitive and page-specific.
+The CLI already falls back from CDP `DOM.setFileInputFiles` (by objectId, then nodeId) to a JS `DataTransfer` assignment. Do not add further JavaScript fallbacks on top; file inputs are security-sensitive and page-specific. If all three transports fail, report the failure to the user instead of scripting around it.
 
 ## Batch
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omniaibot/win-x64",
-  "version": "1.6.3",
+  "version": "1.6.5",
   "description": "omnibot executable for Windows x64",
   "os": [
     "win32"