Contribution plan: strzhao's open PRs (small fixes, HarmonyOS, new features)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- github, node.js, typescript
- Área
- developer-experience, release
Línea de trabajo
Start with the linked pull requests #4282–#4297 and the HarmonyOS extraction tracked in #4317; this issue coordinates their review rather than specifying a standalone code change. Read the direction for section C and the device evidence requirements in section B. There is no single completion condition here: the tracked PRs must be reviewed and landed or their design direction resolved.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
@strzhao thanks for the large batch of contributions. There are 16 open PRs, and a lot of this is useful. To keep review moving and the codebase coherent, we'll take them in a fixed order. This issue tracks it.
Please hold new PRs until the open set is down to about five.
A. Small fixes: landing now
We'll help finish these, and may push small fixes to your branches.
- #4282 docs: route the management command family in the skill and install help
- #4284 render scoped snapshot refs in their pinned form
- #4289 guide screenshot callers to the session prerequisite
B. HarmonyOS: one at a time, with committed evidence
CI has no HarmonyOS device or HDC lane, so green CI only proves the mocked unit tests. For each device-facing change, please commit the live run as an evidence file under docs/evidence/ (device, build, commands, output), and propose a landing order. We'll review them one at a time.
- #4239 inject gesture pan as a densified touch-panel trajectory
- #4285 report the keyboard band in snapshot responses
- #4287 lower
open --launch-argstoaa startparameters - #4290 keep-awake on and off across Android and HarmonyOS
- #4292 support app uninstall beside deploy
- #4293 verify foreground after open instead of trusting the launch line
- Parked: #4240, the experimental test-HAP carrier for locked-down builds. It's about 2k lines of experimental surface we'd have to maintain, so it waits until there's a supported need.
HarmonyOS is moving out of core: #4317 extracts it behind a platform plugin interface and ships it as @agent-device/harmonyos in 0.22, like our other providers and platforms. Changes that land before then move with it.
C. New commands and flags: design first
These add new public CLI and daemon surface without an agreed design. We're reviewing them together for coherence (overlaps such as press sequences versus --expect readback) and for performance impact on paths that don't use them. We'll post a direction per PR here. Where we accept the direction, we'll ask for a short issue (use case, smallest version, CLI example, completion conditions) before review continues. Some may change shape or be declined.
- #4296 atomic multi-ref press sequences
- #4297 guaranteed press baselines and
--expectreadback - #4288 scripted takeover hold and release subcommands
- #4291 burst screenshots with
--countand--interval-ms - #4286 advise sessions stuck in the snapshot-per-action loop
- #4294 advise
session listreaders about cross-workspace claims
Direction for C: design review in progress; posted here when done.
- Lenguaje dominante
- TypeScript
- Estrellas
- 5.3k
- Forks
- 377
- Merge medio
- 13 h 58 min
- PR fusionados (30 d)
- 654
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de callstack/agent-device
-
iOS alert wait: the last poll can get ~30 ms and turns "no alert" into a failed readPosiblemente ocupada @pcbeingused333 la tomó hace 7 días. Abiertobug ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
callstack/agent-device#4018 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
callstack/agent-device#1869 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
callstack/agent-device#4322 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug ready-for-agent
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
callstack/agent-device#4321 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Extract HarmonyOS behind a platform plugin interface, then ship it as @agent-device/harmonyos (0.22)Abiertorefactor
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
callstack/agent-device#4317 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de callstack/agent-device
Issues similares
-
content triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
tensorflow/tfjs#8754 ·
-
tool-submission
Dificultad 1/5 Menos de una hora Aptitud para principiantes 83/100
BraveOPotato/NoSignups#2348 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
code-yeongyu/oh-my-openagent#12784 ·
Los mantenedores suelen responder en 1 día
-
external-issue to-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 71/100
Los mantenedores suelen responder en 1 día