Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Opt-in inactivity expiry for local device claims

Open
#2,833 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cli, node.js, typescript
Domain
backend-api-design, cli, devtools

Research direction

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.

Written by the indexing model from the issue text.

Description

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!

Dominant language
TypeScript
Stars
4.7k
Forks
304
Avg merge
11h 29m
Merged PRs (30d)
514

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from callstack/agent-device

All issues in callstack/agent-device

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.