Opt-in inactivity expiry for local device claims
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- cli, node.js, typescript
- Área
- backend-api-design, cli, devtools
Línea de trabajo
Look at the local device ownership and session management code, likely around the daemon and device claim logic. Review issues #1320 and #2162 for context on the design and existing --stale release command. The new environment variable AGENT_DEVICE_SESSION_IDLE_TIMEOUT_MS needs to be integrated to track command activity and trigger session closure, similar to proxy lease expiry. Check how sessions are currently closed and claims released.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the feature
An opt-in idle timeout for local sessions, off by default. For example, AGENT_DEVICE_SESSION_IDLE_TIMEOUT_MS. When a session gets no commands for that long, the daemon closes it the normal way and releases its device claim.
Motivation
Several AI agents share one computer and a few devices. Agents often finish without running close, so their claims stay live until the daemon stops. Other agents then get DEVICE_IN_USE and can't tell an active session from an abandoned one.
We know #1320 made "never reclaim a live owner because it looks inactive" a deliberate rule, and that's a good default. We're asking for this only as an opt-in for machines shared by agents. Proxy leases already expire after 5 minutes without commands, so this would bring the same behavior to local devices.
Related Issues
- #1320: local device ownership design, including the inactivity non-goal
- #2162: added
device release --stale, without--force
Written by Claude Opus 5.5
Hope you guys take AI issues 😆
Thanks!
- Lenguaje dominante
- TypeScript
- Estrellas
- 4.7k
- Forks
- 304
- Merge medio
- 11 h 29 min
- PR fusionados (30 d)
- 514
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
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
callstack/agent-device#2842 ·
-
docs(ios-runner): RUNNER_PROTOCOL.md points at the wrong file and omits recovery and busy codes Abiertodocumentation good first issue ready-for-agent
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
callstack/agent-device#2797 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
callstack/agent-device#1869 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
callstack/agent-device#2856 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
callstack/agent-device#2853 ·
Todos los issues de callstack/agent-device
Issues similares
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Crush Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
ElementsProject/cln-application#167 · 1 comentario · 1 reacción ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Quantco/pnpm-licenses#17 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100