claude-code - 💡(How to fix) Fix /export produces 0-byte .txt files [1 comments, 2 participants]

TL;DR

The /export command is likely failing to write content to the generated .txt file due to an issue with the text serialization process, despite the session data being intact in the JSONL files.

Guidance

• Verify that the JSONL files in ~/.claude/projects/<project>/<uuid>.jsonl contain the expected data by checking their size (1-3MB each) and contents using a JSONL parser or viewer.
• Check the Claude Code version (2.1.110) for any known issues or bugs related to the /export command or text serialization.
• Manually parse the JSONL files to readable text as a temporary workaround, as described in the issue's Workaround section.
• Investigate the text serialization process in the Claude Code to identify potential issues, such as encoding problems or data formatting errors.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue seems to be specific to the /export command and text serialization, and not related to the underlying session data or JSONL files. The workaround provided in the issue can be used to manually convert the session data to readable text.

Recommendation

Apply the workaround by manually parsing the JSONL files to readable text, as the root cause of the issue is not yet identified and a fix is not available. This will allow users to access their session data in a readable format until the issue is resolved.