claude-code - 💡(How to fix) Fix Claude Code fills entire disk via /tmp/claude-{uid} temp files (771 GB crash loop) [1 participants]

Claude configuration file at /Users/mini/.claude.json is corrupted: JSON Parse error: Unable to parse JSON string The corrupted file has been backed up to: /Users/mini/.claude/backups/.claude.json.corrupted.1775866517894 A backup file exists at: /Users/mini/.claude/backups/.claude.json.backup.1775865061735

TL;DR

To prevent Claude Code from filling the disk with temporary files and entering a restart loop, implement a size limit for temporary files and auto-restore the configuration from a backup when corruption is detected.

Guidance

1. Implement temporary file size limit: Introduce a maximum size cap (e.g., 5 GB) for /tmp/claude-{uid} directories to prevent excessive disk usage.
2. Auto-restore configuration from backup: Modify Claude Code to automatically restore the configuration from a detected backup when corruption is found, instead of crashing and restarting.
3. Add a circuit breaker mechanism: Implement a circuit breaker that stops Claude Code from restarting after a specified number of crashes within a certain time frame, logging a clear error message instead.
4. Monitor disk space and temporary files: Regularly monitor the disk space and temporary files to detect potential issues before they cause significant problems.
5. Review backup and restore mechanisms: Ensure that the backup and restore mechanisms are functioning correctly and that backups are regularly created to prevent data loss.

Example

# Example of how to implement a simple cleanup script for temporary files
# This script assumes a maximum size of 5 GB for /tmp/claude-{uid} directories
find /private/tmp/claude-501 -type f -size +5G -delete

Note: This is a basic example and may need to be adapted to the specific requirements of Claude Code.

Notes

• The suggested fixes and workaround are based on the information provided in the issue and may require modifications to the Claude Code application.
• Implementing these changes may require additional testing to ensure they do not introduce new issues.

Recommendation

Apply the suggested fixes, including implementing a size limit for temporary files, auto-restoring the configuration from a backup, and adding a circuit breaker mechanism, as these changes address the root causes of the issue and can help prevent similar problems in the future.