Skip to content
PidebugCLI & tooling

Test select_range AX command in TextEdit automation tool

Session from pi-computer-use-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk

47ssession
0interventions
GOAL

Verify a new select_range API call by highlighting a text substring in TextEdit and replacing it via type_text, then reporting the resulting AX value.

  1. Prompt · +0
    Screenshot TextEdit, use select_range to highlight 'middle', type_text to replace with 'REPLACED', then quote the final AX value.
  2. Agent did · +0m
    Took screenshot of TextEdit and captured semantic window state showing the AXTextArea with text 'before middle after'.
  3. Fail · +0m
    select_range call failed twice with 'Unknown command setSelectedTextRange', both with and without window param.
  4. Agent did · +0m
    Re-captured window state to confirm current AX text before trying an alternate approach.
  5. Agent did · +0m
    Worked around the missing select_range support by using set_text to directly replace the full string with 'before REPLACED after\n'.
  6. Outcome · +0m
    Final AX value confirmed as 'before REPLACED after\n', achieved via set_text fallback since select_range command was unimplemented.
VERDICT

I'd flag upfront that select_range might not be implemented yet so the agent doesn't waste two calls discovering the same error. The workaround of using set_text to directly rewrite the whole string is what actually got the job done here, not the intended select_range+type_text flow.

I tried this · 0

Discussion · 0

How Builds work