session_logs

Locate active Claude Code session logs and summarize tool usage and conversation history.

4|1|Updated May 19, 2025

Search Tags:#debugging #analysis #claude-code #conversation-history #session-logs #tool-usage #session-discovery

Ready to run

npx skills add https://github.com/agentydragon/ducktape --skill session-logs-agentydragon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session_logs
Source: https://github.com/agentydragon/ducktape/tree/main/nix/home/claude_code/skills/session_logs
Command: npx skills add https://github.com/agentydragon/ducktape --skill session-logs-agentydragon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq.

What problem does it solve?

Claude Code sessions generate rich activity logs that describe tool usage, user messages, and project context. This skill helps locate the active session log under ~/.claude/projects/, extract meaningful metadata, and prepare summaries for debugging or auditing.

Core Features & Use Cases

Discover the current Claude Code session by inspecting project-specific directories and recent activity.
Extract and summarize tool usage, user messages, and conversation history for analysis and follow-ups.
Support debugging, auditing, and knowledge transfer by providing reliable session file discovery and structured context.

Quick Start

Identify the active Claude Code session log and generate a concise report of recent tool uses and user messages.

Frequently Asked Questions about session_logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find my current Claude Code session logs for debugging?▼

To find Claude Code session logs, locate the active session file under ~/.claude/projects/ by inspecting project-specific directories and recent activity. This skill automates discovery using recency signals and directory naming to return the best matching session file.

Can I extract tool usage history from multiple Claude Code projects?▼

Yes, you can extract tool usage and conversation history from multiple Claude Code projects. This skill applies discovery logic across project directories to compare recent activity and generate structured metadata for auditing and follow-up analysis.

What is the best way to analyze conversation history from Claude Code sessions?▼

The best way to analyze conversation history is to extract and summarize tool usage and user messages from session logs. This skill locates the active session file and prepares structured context summaries for debugging or knowledge transfer.

Does session log discovery require any specific command-line tools?▼

Session log discovery requires jq, a command-line JSON processor. This dependency is used to parse and extract meaningful metadata from the raw session log files stored under the ~/.claude/projects/ directory structure.

How does Claude Code session discovery identify the active session across different projects?▼

Session discovery identifies the active session by applying robust recency signals, project directory naming conventions, and file-based context. It evaluates these signals across multiple projects to reliably return the best matching session file.

Why are my Claude Code session logs not showing recent tool usage?▼

If session logs are not showing recent tool usage, the discovery logic may be failing to match the correct project directory or recency signals. Ensure your active project is correctly named under ~/.claude/projects/ and that jq is installed for metadata extraction.