/session-end

Cleanup and persist session state before ending work.

BOOST

ruvnet@ruvnet

GitHub

From plugin

ruview

96k92 skills94 agents92 commands1 MCP

Install

> /plugin marketplace add ruvnet/RuView
> /plugin install ruview@ruview

How it fires

How this command gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/session-end

Context preview

What this command does when you run it.

Cleanup and persist session state before ending work.

Command definition

session-end.md

hook session-end

Cleanup and persist session state before ending work.

Usage

npx claude-flow hook session-end [options]

Options

`--session-id, -s <id>` - Session identifier to end
`--save-state` - Save current session state (default: true)
`--export-metrics` - Export session metrics
`--generate-summary` - Create session summary
`--cleanup-temp` - Remove temporary files

Examples

Basic session end

npx claude-flow hook session-end --session-id "dev-session-2024"

With full export

npx claude-flow hook session-end -s "feature-auth" --export-metrics --generate-summary

Quick close

npx claude-flow hook session-end -s "quick-fix" --save-state false --cleanup-temp

Complete persistence

npx claude-flow hook session-end -s "major-refactor" --save-state --export-metrics --generate-summary

Features

State Persistence

Saves current context
Stores open files
Preserves task progress
Maintains decisions

Metric Export

Session duration
Commands executed
Files modified
Tokens consumed
Performance data

Summary Generation

Work accomplished
Key decisions made
Problems solved
Next steps identified

Cleanup Operations

Removes temp files
Clears caches
Frees resources
Optimizes storage

Integration

This hook is automatically called by Claude Code when:

Ending a conversation
Closing work session
Before shutdown
Switching contexts

Manual usage in agents:

# At session end
npx claude-flow hook session-end --session-id "your-session" --generate-summary

Output

Returns JSON with:

{
  "sessionId": "dev-session-2024",
  "duration": 7200000,
  "saved": true,
  "metrics": {
    "commandsRun": 145,
    "filesModified": 23,
    "tokensUsed": 85000,
    "tasksCompleted": 8
  },
  "summaryPath": "/sessions/dev-session-2024-summary.md",
  "cleanedUp": true,
  "nextSession": "dev-session-2025"
}