Session retention and cleanup policy for cloud-stored sessions

[flohump]

Question

What is the retention/cleanup policy for sessions stored on the Happy cloud server?

Context

Happy creates sessions on the cloud server (api.cluster-fluster.com/v1/sessions) to enable mobile access. Over time, users will accumulate many sessions as they work on different projects and directories.

Questions

1. Automatic Cleanup: Are old/inactive sessions automatically deleted after a certain period?
2. Retention Policy: Is there a retention policy (e.g., delete after 30/60/90 days of inactivity)?
3. Manual Management: Is there a way for users to view and manually delete old sessions?
   • Through the web app at https://app.happy.engineering?
   • Through the CLI?
4. Storage Limits: Are there any limits on the number of active sessions per user?

Current Behavior

From the CLI code:

• Sessions are created via POST /v1/sessions with a tag
• Sessions can be updated but there's no visible deletion mechanism in the CLI
• No indication of expiry or cleanup in the client code

Suggested Enhancement

If sessions don't automatically expire, consider:

• Implementing automatic cleanup after X days of inactivity
• Adding a CLI command like happy sessions list and happy sessions delete <session-id>
• Showing session management in the web app
• Adding a happy doctor clean-sessions option to remove old sessions

This would help prevent unbounded storage growth and give users control over their session data.