find-session-id

Identify the origin Claude Code session for a quoted snippet from JSONL logs.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/KangOxford/auto-quant-research --skill find-session-id
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-session-id
Source: https://github.com/KangOxford/auto-quant-research/tree/main/execution-layer/skills/find-session-id
Command: npx skills add https://github.com/KangOxford/auto-quant-research --skill find-session-id

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locate the exact origin Claude Code session that produced a user-quoted output by tracing across historical session logs and filtering out active workstreams.

Core Features & Use Cases

  • Cross-session provenance: searches JSONL session logs for the quoted snippet and aggregates per-file match counts to identify the most probable origin.
  • Deterministic output: returns a compact, auditable six-field result including session ID, size, modified timestamp, match count, path, and a resume command.
  • Safe tracing: excludes sessions that are currently active to avoid confusion when multiple runs occur.

Quick Start

Provide the quoted text and run the skill to locate the origin session.

Frequently Asked Questions about find-session-id

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

FAQPage Schema
How do I find which Claude Code session produced a specific output snippet?

To find which Claude Code session produced a specific output snippet, you provide the quoted text and the skill searches historical JSONL session logs, aggregating per-file match counts to identify the exact origin session.

Can I trace a quoted text snippet across historical logs without matching active sessions?

Yes, you can trace quoted text snippets safely because the search explicitly excludes currently active sessions from the JSONL log analysis, preventing confusion when multiple workstreams are running simultaneously.

How does cross-session provenance matching work for JSONL log analysis?

Cross-session provenance matching works by searching JSONL session logs for the quoted snippet and selecting the origin session based on the highest per-file match count, ensuring accurate and auditable results.

What details are included in the deterministic output when locating a session ID?

The deterministic output includes a compact six-field result containing the session ID, file size, modified timestamp, match count, file path, and a resume command for quick reuse.

What is the best way to resume a historical Claude Code session found by quoted text?

The best way to resume a historical Claude Code session found by quoted text is to use the resume command provided in the deterministic output, which gives you the exact session ID and path for quick reuse.

Why does my session trace return multiple matches instead of one definitive origin?

If a session trace returns multiple matches, the skill resolves the ambiguity by ranking historical logs based on the highest per-file match count to select the single most probable origin session.