finding-old-chats

Find Claude Code chat transcripts by local date with UTC timezone handling.

4|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/AMindToThink/claude-code-settings --skill finding-old-chats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding-old-chats
Source: https://github.com/AMindToThink/claude-code-settings/tree/main/skills/finding-old-chats
Command: npx skills add https://github.com/AMindToThink/claude-code-settings --skill finding-old-chats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reliably find Claude Code chat transcripts from a past local date or time range, avoiding timezone mistakes that can hide late-night sessions or misclassify a day’s work.

Core Features & Use Cases

  • Local-day transcript search: Scans Claude Code JSONL session logs under the project transcripts directory and matches them by real activity window instead of naive date-string matching.
  • Timezone-safe review: Converts local dates to the correct UTC interval so chats that cross midnight are still included in the day the user actually experienced.
  • Unfinished session triage: Flags chats whose last assistant turn looks like an unanswered question, helping you quickly resume incomplete work or review pending threads.

Quick Start

Ask the skill to find all Claude Code chats from a specific date in your local timezone and summarize the matching sessions.

Frequently Asked Questions about finding-old-chats

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

FAQPage Schema
How do I find Claude Code chat transcripts from a specific local date?

Cross-midnight Claude Code sessions are preserved by testing interval overlaps against your local timezone range. This prevents misclassifying late-night work by ensuring the chat matches the day you actually experienced.

Can I check which Claude Code sessions were left unfinished yesterday?

You can triage unfinished Claude Code sessions by filtering non-user echoes and flagging likely unanswered assistant turns. This allows you to quickly identify and resume incomplete work from your past local time ranges.

Why does naive date string matching fail for Claude Code JSONL logs?

Naive date string matching fails for Claude Code JSONL logs because timestamps are recorded in UTC. Direct string matching misses late-night sessions and misclassifies cross-midnight activity, requiring proper UTC interval overlap testing instead.

Does reviewing past Claude Code chats require parsing UTC timestamps?

Reviewing past Claude Code chats requires parsing UTC timestamps to correctly map them to your local day. This timezone conversion is necessary to accurately retrieve session logs without dropping late-night activity.

What is the best way to triage pending threads in Claude Code project logs?

The best way to triage pending threads in Claude Code project logs is to scan for chats whose last assistant turn looks like an unanswered question. This flags likely incomplete sessions for immediate follow-up.