Glitch Project Filesystem Persistence Limits for /tmp Directory

Container Persistence and Temporary Storage

Glitch projects utilize a persistent filesystem that retains changes across container restarts and sleep cycles. This allows application state and configuration files to remain intact when a project wakes up following a period of inactivity.

However, the environment distinguishes between the project root and the /tmp directory. While the root directory is designed for long-term storage, the /tmp directory is subject to different lifecycle rules during container recycling or forced restarts due to resource throttling.

When designing a system that requires temporary caching or session-based file storage, it is unclear how the platform handles the cleanup of /tmp relative to the project's sleep cycle.

• Does the /tmp directory persist across a standard sleep-and-wake cycle?
• At what specific event is the /tmp directory cleared?