Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Argument errors in system_key and desktop_wait that agents trip on

Cerrado
  • ¿Algo no está bien?
#199 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #220 de @iamnbutler — fusionado

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
macos, swift
Área
desktop-dev

Línea de trabajo

Start with the MCP tool schemas and implementations for desktop_system_key and desktop_wait, then trace click handling and post-click observation timing. Validate that return aliases enter, responses identify the frontmost app, and the wait schema documents required fields and timeout bounds. Done means calls succeed on the first attempt with accurate feedback, and observation does not report a click as unchanged before its effect is visible.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Seen 2026-10-23 with Desktop Tools 0.17.1 (app and MCP), driving Ace Canary on macOS 27. Ace is an Electrobun app, so its UI is a WKWebView. The agent was a foreground Claude Code session recording demo videos.

Small schema issues that each cost a failed call:

  • desktop_system_key with return fails with "Choose a named key or one printable character." enter works. Accept return as an alias, since it's the key's name on a Mac.
  • Every desktop_system_key call comes back as unknown: "The keys went to whatever was frontmost; their effect was not read back." That's fair for the route, but it should say which app was frontmost when the keys were sent.
  • desktop_wait with element_appears needs both role and title, and element_gone needs element. The schema doesn't say so. timeout_ms must be an integer from 100 to 45000. List those constraints in the tool description so the first call is right.
  • An element click on Ace's New channel button returned completed while the next observation looked unchanged, yet the channel had been created. The observation after a click may be read too early.
Lenguaje dominante
Swift
Estrellas
0
Forks
0
Merge medio
39 min
PR fusionados (30 d)
162

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/desktop-tools

Todos los issues de githubnext/desktop-tools

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.