get-history-filename

Locate JSONL transcript files for Claude Code and Codex sessions via tmux pane tracing.

1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/tcdent/dotfiles --skill get-history-filename
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: get-history-filename
Source: https://github.com/tcdent/dotfiles/tree/main/agent/skills/get-history-filename
Command: npx skills add https://github.com/tcdent/dotfiles --skill get-history-filename

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps identify the location of the conversation transcript file for an agent session, whether it's for your own session or a peer's, making it easy to access chat history stored on disk.

Core Features & Use Cases

  • Session Transcript Locating: Determines the path of the JSONL transcript file associated with a running agent session.
  • Agent-Specific: Tailored for Claude Code and Codex agent sessions.
  • Use Case: When you need to find the chat history file for a particular session, this Skill can pinpoint its location on disk.

Quick Start

Use the get-history-filename skill with no arguments to find the current session's transcript, or pass a tmux pane ID to find a peer's session transcript.

Frequently Asked Questions about get-history-filename

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

FAQPage Schema
How do I locate the JSONL transcript file for a running Claude Code or Codex session?

To locate the JSONL transcript file for a running agent session, trace the tmux pane to the process to the working directory and finally to the project directory. This Skill automates that process tracing to pinpoint the exact disk-based conversation history file path.

Can I find the chat history file for a peer's agent session in a different tmux pane?

Yes, you can find a peer's chat history file by passing their specific tmux pane ID as an argument to the Skill. It traces that pane's process to locate the associated JSONL transcript file on disk.

How does tmux process tracing map a running agent to its conversation history file on disk?

Tmux process tracing maps a running agent to its conversation history file by following the execution chain from the tmux pane, to the active process, to the working directory, and resolving the project directory where the JSONL transcript is stored.

Do I need tmux and process information access to find an agent's disk-based transcript?

Yes, you need access to tmux and system process information to find an agent's disk-based transcript. The Skill relies on tracing the tmux pane and process hierarchy to resolve the working directory and locate the JSONL file.

What is the best way to get the conversation transcript location for Claude Code sessions?

The best way to get the conversation transcript location for Claude Code sessions is to use a tracing utility that maps the tmux pane to the working directory. This Skill specifically supports Claude Code and Codex sessions to resolve the JSONL file path.

Why does finding an agent session transcript file require tracing the working directory?

Finding an agent session transcript file requires tracing the working directory because the JSONL chat history is stored relative to the project directory. Tracing the tmux pane and process ensures the correct project path is resolved for file system navigation.