Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

No usable route to type into a web text field when the app loses keyboard focus between calls

Aperta
  • Qualcosa non va?
#177 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
macos, swift
Ambito
desktop, developer-experience

Direzione di ricerca

Start by tracing the desktop_insert, desktop_set_value, and desktop_focus tool entry points and the refusal hints described in the issue; the payload names no source files or tests. Compare ways to deliver text when the target window loses keyboard focus, including the suggested foreground typing or atomic focus-and-type routes. Done means text entry works reliably in the described Safari scenario and the hint no longer recommends a refused route.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What happened

Filling a text input on a React page (Proton VPN's WireGuard config form) in
Safari. The agent runs from a terminal, so the terminal keeps taking keyboard
focus back between tool calls. Every available route refuses, and two of the
refusals point at each other:

desktop_insert route=type
→ "Invalid target: Exact-window keyboard focus is not on the target window at
   dispatch... To write into this window without focusing it, observe it and
   set its editable element's accessibility value (`set-value` command,
   `set_value` tool)."

desktop_set_value
→ "Set a date as ISO 8601... Use desktop_type for text."

insert says use set_value; set_value says use typing. For a text field in
a window that doesn't hold keyboard focus there is no route that succeeds.

desktop_focus does work, but focus is lost again before the next call lands
(each action needs a fresh snapshot, and the terminal reclaims focus in
between), so focus → inspect → insert is racy and failed repeatedly.

Why set_value is refused here is understandable

I'm aware AX value writes on web inputs don't fire JS input/change events, so
React would keep the old value — that's documented behaviour and refusing is
reasonable. The problem is that no alternative is offered for this situation.

Suggestions (any one would unblock)
  1. A foreground typing route — activate the app, type with real keys,
    return unknown with a readback, consistent with how modifier-clicks and
    drags already work.
  2. Make desktop_focus + type atomic, so focus can't be lost between the
    observation and the dispatch.
  3. Let expect on desktop_focus gate until the window actually holds
    keyboard focus, so the agent can sequence reliably.

The refusal hint should also not recommend set_value for a text field, since
that path is unconditionally refused.

Environment

Desktop Tools 0.16.1, macOS 27, Safari 27, agent running from Ghostty

Lingua principale
Swift
Stelle
0
Fork
0
Merge medio
39m
PR unite (30g)
144

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/desktop-tools

Tutte le issue di githubnext/desktop-tools

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.