fix: dev-poll stale issue detection checks for dead tmux sessions instead of agent assignment #324
Labels
No labels
action
backlog
blocked
bug-report
in-progress
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
tech-debt
underspecified
vision
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#324
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
dev/dev-poll.sh lines 396-411 detect stale in-progress issues by checking if a tmux session exists:
With the migration to claude -p (agent-sdk.sh), there are no tmux sessions. Every in-progress issue without an open PR gets incorrectly flagged as stale, even when another container's agent is actively working on it.
Observed on #303: dev-bot's dev-poll flagged it as stale while dev-qwen was actively implementing it in the other container.
Fix
Replace the tmux session check with an assignee check. If the issue has an assignee, trust that the assigned agent is working on it:
Only flag as stale if: no assignee AND no open PR AND no dev-agent lock file for this project.
Also remove the tmux helper function at line 101-107 (is_session_alive) and the tmux has-session calls — these are remnants of the dead tmux code path.
Affected files
Acceptance criteria
Stale in-progress issue detected
no_active_session_no_open_pr2026-04-06T20:14:02ZStatus: This issue was labeled
in-progressbut no active tmux session exists.Action required: A maintainer should triage this issue.