Repository navigation
Manual verify: Ralph idle-watch (#31) #419
Description
Feature: Ralph's idle-watch — monitors for stale work and nudges team.
Why manual verification needed:
- Requires time-based triggers (idle threshold detection)
- Involves polling and state tracking over extended periods
- Hard to simulate realistic idle scenarios in unit tests
Test approach:
- Start a squad session with an issue assigned to an agent
- Let the agent go idle (no activity for N minutes)
- Verify Ralph detects the idle state and posts a nudge
- Resume work and verify Ralph stops nudging
- Test threshold boundaries (e.g., 5 min idle vs 10 min)
- Test with multiple agents (some idle, some active)
Success criteria:
- ✅ Ralph detects idle agents within expected time window
- ✅ Nudges are posted appropriately (not too aggressive)
- ✅ Active agents are not flagged as idle
- ✅ Idle detection works across session restarts
- ✅ No false positives during legitimate pauses
Related: Issue #31
Activity
github-actions commentedon Mar 15, 2026
📋 Assigned to FIDO (Quality Owner)
Issue: #419 — Manual verify: Ralph idle-watch (#31)
FIDO will pick this up in the next Copilot session.
test: SDK feature parity tests for #340
test: SDK feature parity tests for #340 (#422)
Fix github#421: Lead with default behavior in --help (github#438)
bradygaster commentedon Mar 24, 2026
Closing for now — will reopen once SDK-first (#341, #347) is complete. Ralph idle-watch verification depends on SDK parity being finished first.