Add session-status skill to triage claude agents sessions#10
Open
udnisap wants to merge 1 commit into
Open
Conversation
Consolidated readout of active `claude agents` (FleetView) background sessions — what each is working on and what input it needs to unblock. Driven by `claude agents --json` plus persisted transcripts under ~/.claude/projects (claude logs is unreliable for exited processes). Offers to stop stale sessions and surfaces attach commands. Claude-Session: https://claude.ai/code/session_01FP7L7pH557LQjN4Qmz8aJT
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
1 participant
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.
What
Adds a global
session-statusskill underclaude/skills/session-status/that gives a consolidated readout of all activeclaude agents(FleetView) background sessions — what each is working on and, crucially, what input it needs to unblock.FleetView sessions are peers with no cross-session control, so this is a reporting/triage tool, not an orchestrator.
How it works
claude agents --json.~/.claude/projects/<escaped-cwd>/<sessionId>.jsonland extracts the first user message (the task) and the last assistant message (what it's waiting on).claude logs— it only works while a session's process is alive and returns raw ANSI, so it's unreliable for the (mostly exited) blocked sessions.--jsonmode emits one structured object per session for programmatic use.MM/DD/YYdates, thousands separators, one-decimal percentages.Files
claude/skills/session-status/SKILL.md— instructs Claude to run the script, present oldest-first, flag parked/finished sessions, and offer confirmation-gatedclaude stop/ surfaceclaude attachcommands.claude/skills/session-status/session-status.sh— the engine (bash + jq).Sits alongside the existing
claude/skills/tmux-splitskill. Verified end-to-end against a live fleet of 28 active sessions (exit 0, all rendered with populated "waiting on" lines).https://claude.ai/code/session_01FP7L7pH557LQjN4Qmz8aJT