Current behavior

SessionNeedsAttention() (internal/data/session.go:88-91) returns true for exactly two statuses:

• "needs-input" — session waiting for user input
• "failed" — session has failed

Idle sessions, stale sessions, and sessions inactive for hours are explicitly not considered needing attention. The constants AttentionStaleThreshold (20 min) and AttentionStaleMax (4 hours) exist but are only used for SessionIsActiveNotIdle, not for attention.

Questions to resolve

1. Should long-idle "running" sessions need attention? A session marked "running" but silent for 2+ hours might be stuck. Should there be a "possibly stuck" attention state?

2. Should "queued" sessions that have been waiting too long need attention? A session queued for 30+ minutes might indicate a problem.

3. Should sessions with CI failures need attention? If a session's PR has failing checks, should that surface as needing attention even if the session status is "completed"?

4. Graduated attention levels? Instead of binary needs-attention, consider levels like:

   • 🔴 Urgent — failed, needs-input
   • 🟡 Warning — idle too long, possibly stuck
   • 🟢 Info — completed with warnings

5. Should the attention threshold be user-configurable? The 20-minute idle threshold is hardcoded — some users might want more or less sensitivity.

Current usage points

• Filter tab: a key jumps to attention view
• Mission dashboard: "Needs your attention" section with contextual messages
• Task detail: inline attention banner with reason
• Header: badge count for attention items

References

• internal/data/session.go:88-91 — core logic
• internal/tui/helpers.go:251-285 — filtering and counting
• internal/tui/components/mission/mission.go:154-173 — dashboard display
• internal/tui/components/taskdetail/taskdetail.go:244-256 — detail view reasons