Session Cleanup
Identify stale and empty Claude Code sessions in the Agent Monitor and explain the...
Install
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-cleanup -g -a claude-code -y- Repository
- hoangsonww/Claude-Code-Agent-Monitor1.1k
- Category
- Data and ML
- Updated
- 5d ago
- License
- MIT
- Context cost
- Lightabout 730 tokens
- Runs scripts
- No, instructions only
What it does
Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation. Use when tidying the monitoring database.
Session Cleanup
Find prune-worthy sessions and explain cleanup, preview first, delete only on explicit confirmation.
Input
The user provides: $ARGUMENTS
- Empty /
preview→ only show what would be removed (the safe default). confirm→ the user has reviewed the preview and explicitly authorizes deletion.- An optional staleness threshold (e.g.
older than 7d) for what counts as stale.
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/sessions?limit=N | session list: id, status, model, cwd, started_at, ended_at, cost, metadata (turn_count, total_turn_duration_ms) |
GET /api/stats | totals: total_sessions, active_sessions, total_events, events_today, sessions_by_status, agents_by_status |
POST /api/settings/cleanup | runs the cleanup routine and returns what was removed, DESTRUCTIVE, only after confirmation |
Report Sections
1. Baseline
GET /api/stats, record total_sessions, sessions_by_status, total_events. This is
the before-state to compare against.
2. Identify candidates
GET /api/sessions?limit=1000. Flag sessions that are:
- Empty, zero events and
turn_count0 / null andcost0 (started but never did anything). - Stale active,
statusactive/working but last activity older than the threshold (default 24h), i.e. never cleanly stopped. - Truncated, no
ended_atand no recent events.
3. Preview table (ALWAYS shown)
List every candidate with the reason it qualifies. State the total count and confirm that nothing has been deleted yet.
4. Explain the endpoint
Describe POST /api/settings/cleanup: it prunes empty / orphaned sessions and their
dangling events server-side and returns a summary of removed rows. Make clear this
is permanent and not reversible from the dashboard.
