Skill

view-team-session

Generates self-contained HTML viewer for Claude Code sessions including agent teams with inter-agent DM timelines, filtering, search. Use for viewing, replaying, or inspecting JSONL logs by session ID.

Python

Html

Bash

developer-tools

Install

npx claudepluginhub prince-khanna/claude-code-plugins --plugin agent-teams

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Generate a self-contained HTML viewer from Claude Code session JSONL logs.

Supporting Assets

assets/template.htmlscripts/generate.py

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

169.2k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

169.2k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

169.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 13, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

View Team Session

Generate a self-contained HTML viewer from Claude Code session JSONL logs. Works for both solo sessions and agent team sessions, showing the full conversation timeline with filtering, search, and collapsible tool calls.

How It Works

Claude Code stores conversation logs as JSONL files at ~/.claude/projects/<project>/<session-id>.jsonl. When agent teams are used, each agent gets its own JSONL file in the same project directory, linked by a shared teamName field. Team config is stored at ~/.claude/teams/{team-name}/config.json.

Browsers can't read local JSONL files directly, so the skill uses a Python script to extract the data and embed it into a self-contained HTML playground.

Usage

Run the generate script with a session ID using uv run:

uv run ${CLAUDE_SKILL_DIR}/scripts/generate.py SESSION_ID [--output path] [--no-open]

SESSION_ID — the UUID from the JSONL filename (e.g., 605eef0e-40be-4e0f-8a34-0a977c60399d)
--output path — custom output path (default: .claude/output/<session-id>.html)
--no-open — skip auto-opening in browser

The script will:

Scan ~/.claude/projects/*/ to find the session's JSONL file
If it's a team session, discover all teammate JSONL files via the shared teamName field and enrich with team config from ~/.claude/teams/
Parse all files into structured events (speech, DMs, tool calls, task management, thinking, etc.)
Deduplicate inter-agent DMs (each DM exists in both sender and receiver logs — only the sender's copy is kept since it has richer metadata)
Embed the data into the HTML template and write the output file

Finding Session IDs

If the user doesn't provide a session ID, help them find one:

# List recent sessions for the current project
ls -lt ~/.claude/projects/<project>/*.jsonl | head -10

# Search for sessions containing specific content
grep -l "search term" ~/.claude/projects/<project>/*.jsonl

The session ID is the filename without the .jsonl extension.

Output

The generated HTML is a single self-contained file with:

Header showing team name, session ID, duration, event count
Sidebar with agent toggles, event type filters, and content search
Timeline of event cards with agent-colored borders
Task management events highlighted (task creation, assignment, completion, dependencies)
Default view shows speech and DMs only; tool calls, thinking, and system events are togglable
Dark theme (GitHub-dark style)

Output files go to .claude/output/ by default.