Conversation Logging FAQs

Question 1

Can I run multiple Claude sessions simultaneously?

Accepted Answer

Yes. The skill uses unique session IDs and process IDs to ensure each concurrent Claude instance writes to its own specific log file without conflicts.

Question 2

How do I provide a previous log's context back to Claude?

Accepted Answer

You can reference any log file in a new Claude session using the @ symbol followed by the path to the log, allowing Claude to read and resume previous work.

Question 3

Is it possible to automatically delete old logs?

Accepted Answer

Yes, the skill includes a prune-logs.sh script that can be run manually or via a cron job to delete logs older than a specified number of days.

Question 4

Are these logs encrypted?

Accepted Answer

No, logs are stored as plain-text markdown files. Users should treat them as sensitive data and follow the provided security recommendations, such as regular pruning and backup exclusions.

Question 5

Where are the conversation logs stored?

Accepted Answer

By default, logs are stored in markdown format within the ~/.claude/conversation-logs directory, though this path can be customized in the hook script.

Conversation Logging

About

Key Features

Use Cases

Conversation Logging

About

Key Features

Use Cases