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

feat: workspace-scoped device pinning (lock a project to one device)

Abierto
  • ¿Algo no está bien?
#2,161 2 comentarios 0 reacciones 0 asignados Ver en GitHub

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
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
cli, mobile-dev

Línea de trabajo

Empieza rastreando la selección de dispositivos para mutaciones abiertas y sin sesión, como boot e install, y la selección basada en el inventario. Lee la ayuda actual de la CLI y el manejo de conflictos de selección; después, identifica cómo devices y doctor podrían exponer un pin activo. Se considera terminado cuando los comandos fijados nunca hacen fallback, los selectores en conflicto fallan con detalles estructurados y el escape hatch está documentado.

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

Descripción

needs-triage

Motivation

User feedback (local-environment, client project):

I had tons of issues with agent-device always trying to open iPhone simulator (default) when I really wanted the session to be scoped to a particular iPad only when I was working with real client's project. Solved it by wrapping every agent-device command with my custom bash script. I think simlock might be a good tool to enforce that.

Today the only way to target a specific device is to pass --platform/--device/--udid/--serial on every invocation. When an agent (or human) forgets, inventory selection falls back to its booted-device heuristics and picks the default iPhone simulator — on a client project that is not a nuisance but a correctness failure. Users are resorting to wrapper scripts to enforce scoping.

This is adjacent to but distinct from #1320: device claims fence other worktrees' daemons off a device; they do nothing to stop your own commands from selecting the wrong device. Enforcement of user intent at selection time is the missing piece.

Proposal

A workspace-scoped device pin that both defaults and enforces:

  • A pin source, in precedence order: env (AGENT_DEVICE_PIN-style selector) and/or a per-workspace config the daemon/CLI reads from the project root. The repo currently has no project config file surface, so the env form may be the v1.
  • Selector-less commands inherit the pin: open com.example.app targets the pinned iPad, never the default iPhone.
  • Commands with an explicit selector that CONTRADICTS the pin fail with a structured error naming the pin and its source — consistent with the #1880 principle that selection conflicts fail instead of retargeting. (An explicit selector that refines the pin — same device — passes.)
  • devices/doctor surface the active pin so agents can discover why selection is constrained.
  • The error and --help text must teach the escape hatch (edit/unset the pin), not invite per-command overrides that defeat the point.

Non-goals

  • Cross-worktree exclusion (that is #1320's device claims).
  • Provider/remote lease semantics.

Acceptance

  • With a pin set and no selector flags, every device-targeting command resolves to the pinned device or fails if it is unavailable — it never falls back to another device.
  • A conflicting explicit selector fails with a structured error naming the pin, its source, and the pinned device.
  • No wrapper scripts required: the pin is honored by open, sessionless mutations (boot, install, ...), and inventory-based selection alike.
Lenguaje dominante
TypeScript
Estrellas
4.9k
Forks
328
Merge medio
12 h 18 min
PR fusionados (30 d)
561

Preparar el entorno

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 callstack/agent-device

Todos los issues de callstack/agent-device

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.