session-scout

name	session-scout
description	Discover and list recent AI coding sessions across Claude Code, Claude Desktop, and OpenCode on Windows and WSL. PowerShell script extracts project paths, session IDs, and timestamps from session artifacts. Use when: finding recent coding sessions, reviewing AI session history, exporting session logs to CSV, troubleshooting missing sessions, or auditing Claude Code/OpenCode usage across environments.
source	plugin

Session Scout

Status: Production Ready Last Updated: 2026-01-27 Dependencies: PowerShell 7+ (pwsh), WSL2 (for WSL session discovery) Script Location: D:\admin\scripts\session-scout.ps1

---

Quick Start (1 Minute)

1. Run the Script

# Show recent sessions (default: top 12)
pwsh -ExecutionPolicy Bypass -File D:\admin\scripts\session-scout.ps1

# Show more sessions
pwsh -ExecutionPolicy Bypass -File D:\admin\scripts\session-scout.ps1 -Top 20

Output columns:

• Tool - Claude Code (Windows/WSL), Claude Desktop, OpenCode CLI/Desktop
• When - Last activity timestamp
• ProjectPath - Working directory path
• Project - Project slug/identifier
• SessionId - UUID (Claude Code) or timestamp (OpenCode)

2. Export to CSV

# Export to default location (~/.admin/logs/session-scout-YYYY-MM-DD.csv)
pwsh -ExecutionPolicy Bypass -File D:\admin\scripts\session-scout.ps1 -Csv

# Export to custom path
pwsh -ExecutionPolicy Bypass -File D:\admin\scripts\session-scout.ps1 -File "D:\exports\sessions.csv"

---

What It Discovers

Claude Code Sessions

• Windows: %USERPROFILE%\.claude\projects\*\*.jsonl
• WSL: ~/.claude/projects/*/*.jsonl (per distro)
• Extracts: cwd, project slug, session UUID

Claude Desktop Sessions

• Windows: %APPDATA%\Claude and %LOCALAPPDATA%\Claude
• Looks for: chat, conversation, transcript, history files

OpenCode Sessions

• Windows: %USERPROFILE%\.local\share\opencode\log\*.log
• WSL: ~/.local/share/opencode/log/*.log (per distro)
• Differentiates: Desktop (multiple dirs) vs CLI (single dir)

---

Critical Rules

Always Do

• Run with pwsh (PowerShell 7+), not Windows PowerShell 5.1
• Use -ExecutionPolicy Bypass when running directly
• Check WSL is running if WSL sessions are missing

Never Do

• Don't modify session .jsonl files directly
• Don't assume all sessions have extractable paths (some may show $null)
• Don't run from inside WSL (script is Windows-native)

---

Known Issues Prevention

This skill prevents 3 documented issues:

Issue #1: UUID-based Filenames Not Found

Error: No sessions found despite active Claude Code usage Why It Happens: Claude Code changed from chat_*.jsonl to UUID-based filenames Prevention: Script uses *.jsonl pattern (excluding agent-*.jsonl)

Issue #2: WSL Distro Names with Null Bytes

Error: WSL sessions not detected, distro names show as U b u n t u Why It Happens: wsl.exe -l -q outputs UTF-16LE with null bytes Prevention: Get-WSLDistros function strips null bytes properly

Issue #3: OpenCode Desktop vs CLI Confusion

Error: All OpenCode sessions showing as same type Why It Happens: Desktop opens multiple projects, CLI opens one Prevention: Script detects pattern - multiple dirs = Desktop, single = CLI

---

Parameters Reference

Parameter	Type	Default	Description
-Top	int	12	Maximum sessions to display
-Csv	switch	-	Export to default path: ~/.admin/logs/session-scout-YYYY-MM-DD.csv
-File	string	-	Export to specified CSV path

---

Session Storage Locations

Claude Code (Windows):
  %USERPROFILE%\.claude\projects\{project-slug}\{uuid}.jsonl

Claude Code (WSL):
  ~/.claude/projects/{project-slug}/{uuid}.jsonl

Claude Desktop:
  %APPDATA%\Claude\
  %LOCALAPPDATA%\Claude\

OpenCode (Windows):
  %USERPROFILE%\.local\share\opencode\log\{timestamp}.log

OpenCode (WSL):
  ~/.local/share/opencode/log/{timestamp}.log

---

Troubleshooting

Problem: No sessions found

Solution: Check expected locations manually:

# Windows Claude Code
dir $env:USERPROFILE\.claude\projects -Recurse -Filter *.jsonl | measure

# WSL Claude Code
wsl -e bash -c 'find ~/.claude/projects -name "*.jsonl" 2>/dev/null | wc -l'

Problem: WSL sessions not appearing

Solution: Ensure WSL is running and distros are accessible:

wsl -l -q

Problem: ProjectPath shows as empty

Solution: Path extraction is best-effort. The session file may not contain a cwd field in the first 100 lines.

---

Example Output

Tool                            When                 ProjectPath                    Project              SessionId
----                            ----                 -----------                    -------              ---------
Claude Code (Windows)           1/26/2026 5:39:03 PM D:\admin                       D--admin             bdeb38c1-98a8-...
Claude Code (WSL:Ubuntu-24.04)  1/26/2026 1:47:28 PM /home/wsladmin/dev/vibe-skills -home-wsladmin-dev-v 3cd316dc-c168-...
OpenCode CLI                    1/26/2026 5:30:37 PM D:\rlm-project                                      2026-01-26T203036
OpenCode Desktop                1/26/2026 1:53:00 PM D:\wireframe-kit                                    2026-01-26T190547
Claude Desktop                  1/26/2026 10:10:18 AM                               sentry               session

---

Integration with Admin Skills

This script is part of the Windows admin toolkit (D:\admin). Session data can be used for:

• Auditing AI tool usage across projects
• Finding previous sessions to resume
• Tracking which projects have active Claude Code configurations
• Exporting session history for documentation

---

Complete Setup Checklist

• PowerShell 7+ installed (pwsh --version)
• Script exists at D:\admin\scripts\session-scout.ps1
• WSL2 installed (for WSL session discovery)
• At least one Claude Code/OpenCode session exists to test

---

Questions? Issues?

1. Run script with -Top 5 to test basic functionality
2. Check storage locations manually if sessions missing
3. Verify WSL distros are accessible with wsl -l -q