feat(text): 'get text' (no selector) defaults to cross-frame whole-page read

So an agent never silently misses iframed content (listing descriptions etc.)
without having to know the --all-frames flag. Single-frame pages are unchanged
(identical to the old body read); multi-frame pages now include child frames —
a strict superset. Skill + help updated to make the default and 'frames'/--main
discoverable.
This commit is contained in:
leeguooooo
2026-06-15 13:42:48 +09:00
parent d4ff49caa8
commit b25958946c
3 changed files with 41 additions and 29 deletions
+4 -5
View File
@@ -1959,8 +1959,7 @@ Usage: chrome-use get <subcommand> [args]
Retrieves various types of information from elements or the page.
Subcommands:
text <selector> Get text content of element
text --all-frames Aggregate text across ALL frames (incl. iframes)
text [selector] Element text; no selector = WHOLE PAGE, all frames
text --main Main-content text only (skip nav/header/sidebar)
html <selector> Get inner HTML of element
value <selector> Get value of input element
@@ -1977,8 +1976,8 @@ Global Options:
--session <name> Use specific session
Examples:
chrome-use get text @e1
chrome-use get text --all-frames # read iframed content (listing pages)
chrome-use get text # whole page across ALL frames (default)
chrome-use get text @e1 # one element
chrome-use get text --main # main content, no nav/sidebar boilerplate
chrome-use frames # list frames + where the text lives
chrome-use get html "#content"
@@ -3190,7 +3189,7 @@ Navigation:
Get Info: chrome-use get <what> [selector]
text, html, value, attr <name>, title, url, count, box, styles, cdp-url
text --all-frames (cross-frame), text --main (no boilerplate), frames (list)
text (no selector = whole page, all frames), text --main, frames (list)
Check State: chrome-use is <what> <selector>
visible, enabled, checked