Test stealth AX mode select_range vs type_text on TextEdit
Session from pi-computer-use-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk
Click a segment to jump to that moment
28ssession
0interventions
GOAL
Verify whether strict AX/stealth mode affects select_range and type_text differently when automating TextEdit via accessibility APIs, and capture any verbatim error messages.
- +0Prompt · +0Screenshot TextEdit, select_range on @e1, confirm it works under stealth mode, then type_text and note if stealth affects it differently. Quote verbatim errors.
- +0mAgent did · +0mTook screenshot of TextEdit window, identified AXTextArea @e1, then ran select_range(start=0,length=-1) which succeeded, selecting range start=0 length=20 under stealth/strict AX mode.
- +0mFail · +0mtype_text call failed under stealth mode with error: raw text insertion is not AX-only; must use set_text, and non-AX/foreground/cursor fallbacks are blocked.
- +0mOutcome · +0mConfirmed select_range works under strict AX/stealth mode but type_text does not; agent quoted the verbatim error and concluded set_text should be used instead of type_text for AX value replacement in stealth mode.
VERDICT
I'd ask upfront to test set_text alongside type_text so the agent could confirm the correct replacement path in one pass instead of just reporting the failure. The select_range test worked cleanly, so no correction was needed there — the useful part was the agent surfacing the exact error text for type_text so I know to switch to set_text under stealth mode.