fix: correct Idle status display in VS Code Copilot Chat#66
Merged
csharpfritz merged 7 commits intomainfrom Feb 22, 2026
Merged
fix: correct Idle status display in VS Code Copilot Chat#66csharpfritz merged 7 commits intomainfrom
csharpfritz merged 7 commits intomainfrom
Conversation
When Squad runs in Copilot Chat, subagents often show Idle because the Squad orchestrator doesn't create active-work marker files. Added fallback detection: if no active-work markers exist but ANY orchestration log file was modified in the last 10 minutes, members who appear in logs are marked as working. This covers the Copilot Chat scenario where logs update but markers aren't created. The active-work marker system remains the primary status indicator when present (5-min staleness threshold). This fallback only activates when no markers exist (10-min activity window). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Root cause: When orchestration logs had #NNN issue references in both relatedIssues AND outcomes, the task was created from relatedIssues first (default to in_progress), missing the completion signal in outcomes. Also: The working-to-idle override was too aggressive - it marked members idle even when they had NO tasks at all (common in Copilot Chat where logs may not have parseable task markers). Changes: - OrchestrationLogService: Check outcomes for completion signals when extracting tasks from relatedIssues - SquadDataProvider: Only apply working-to-idle override when member has tasks but none are in-progress (not when they have zero tasks) - Update test fixture to properly test completion detection Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Add 4 tests for SquadDataProvider working-to-idle override scenarios - Add 4 tests for OrchestrationLogService completion signal detection - Cover edge cases: no tasks, completed tasks, in-progress tasks - Test completion signals: Closed, Resolved, Working on, no outcome Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #63
Summary
Fixes the issue where Squad subagents show 'Idle' in VS Code Copilot Chat when they're actually working.
Root Cause
Task completion detection missed outcomes: When orchestration logs had #NNN issue references in both
elatedIssues\ AND \outcomes, the task was created from
elatedIssues\ first (defaulting to 'in_progress'), missing the completion signal in outcomes like 'Closed Squad CLI version check and upgrade notification #42'.
Overly aggressive working-to-idle override: The logic (working && !currentTask) ? idle\ marked members idle even when they had NO tasks at all — common in Copilot Chat scenarios where logs may not have parseable task markers.
Changes
Test Coverage