Document cloud session TTL and expiration policy for Claude Code on the web

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://docs.anthropic.com/en/docs/claude-code (and research preview notes / troubleshooting guide)

Section/Topic

Cloud session lifecycle, expiration, and TTL — Claude Code on the web (research preview)

Current Documentation

There is no mention of session TTL, expiration policy, or lifetime limits anywhere in the Claude Code on the web documentation, research preview notes, or troubleshooting guide.

What's Wrong or Missing?

Note: This issue is only relevant if issue #50177 is confirmed as intentional behavior (closed as "by design"). If the silent termination is a bug being fixed, this issue can be closed as well.

Based on observed behavior (see #50177), cloud sessions appear to terminate silently after approximately 7 days with no warning and no recovery path. Users who rely on these sessions for ongoing work have no way to know:

• How long a session will persist
• Whether inactivity affects the TTL
• What happens to uncommitted context at expiration
• Whether there is any way to extend or preserve a session
• How to check a session's remaining lifetime

Suggested Improvement

Add the following to the Claude Code on the web docs, research preview notes, and/or troubleshooting guide:

1. The session TTL (e.g., "Sessions expire after 7 days")
2. Whether the TTL resets on activity or is a hard wall from creation time
3. What happens to session data at expiration (is it recoverable?)
4. Best practices for preserving context before expiration (e.g., commit to GitHub)
5. How to check a session's remaining lifetime (if possible)

Impact

High - Prevents users from using a feature

Additional Context

Related issues:

• #50177 — Bug report / root cause
• #30922 — Orphaned sessions (related session lifecycle issue)