session-history

You can search session history by retrieving stored prompts, user intents, and touched files from the ~/.claude/projects path. This allows you to quickly look up session-by-session activity and recover context for ongoing projects without relying on memory.

The best way to lookup past prompts and summaries is to access session data organized under ~/.claude/projects. This mechanism stores user prompts, assistant messages, and auto-generated summaries, enabling fast lookup and continuity for ongoing work.

Yes, you can retrieve current and historical summaries to verify past decisions and understand progress. This access provides auditability and continuity across multiple sessions in ongoing projects by fetching stored assistant messages and auto-generated summaries.

You can list touched files across sessions by accessing the stored session history under the ~/.claude/projects path. This enables you to track workflow changes, review user intents, and verify which files were modified during specific session activities.

Session history lookup works automatically by accessing auto-generated summaries, user prompts, and assistant messages stored under ~/.claude/projects. It requires no external dependencies, relying entirely on the existing stored session data for continuity.

You need to fetch session history when relying on memory slows progress or when you must verify past decisions and actions. It is essential for ongoing projects with multiple sessions where recovering context and ensuring auditability are required.