docs(enterprise): document conversation lifecycle limits and 12h session cap - #718
Open
jpshackelford wants to merge 2 commits into
Open
docs(enterprise): document conversation lifecycle limits and 12h session cap#718jpshackelford wants to merge 2 commits into
jpshackelford wants to merge 2 commits into
Conversation
…ion cap Explain the configurable Idle Time and Deletion Time sandbox settings, and document the non-configurable 12-hour maximum running-session cap. Clarify that these limits are deployment-wide and not settable per conversation or per Agent Profile. Co-authored-by: openhands <openhands@all-hands.dev>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
jpshackelford
marked this pull request as ready for review
August 12, 2026 19:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the time-based limits that govern conversation/sandbox lifetime in OpenHands Enterprise, prompted by customer questions about running conversations indefinitely and whether the idle timeout is configurable globally or per Agent Profile.
The docs previously mentioned "cleaned up due to idle timeout" but did not explain the timers or the hard maximum session duration. This clarifies the behavior without exposing any new configuration.
Changes
enterprise/conversations-and-sandboxes.mdx— new Conversation Lifecycle Limits section explaining:<Note>documenting the 12-hour hard cap on a single running session, which applies even to a continuously-active conversation and is not currently configurable.enterprise/vm-install/admin-console-configuration.mdx— a<Note>under the Sandbox Configuration table cross-referencing the lifecycle page and calling out the non-configurable 12-hour cap.Notes
RUNTIME_MAX_SESSION_SECONDS, default 43200) remains a code/chart default and is intentionally not surfaced as an admin-console/Helm option in this change — this PR only documents existing behavior.sandbox_idle_seconds/sandbox_dead_secondsinOpenHands/OpenHands-Cloud(replicated/config.yaml→ chartRUNTIME_IDLE_SECONDS/RUNTIME_DEAD_SECONDS), and the 12-hour cap is enforced inOpenHands/runtime-apicleanup.py. Agent Profile models in the SDK/enterprise expose no lifetime/session fields.This PR was created by an AI agent (OpenHands) on behalf of the requesting user.
@jpshackelford can click here to continue refining the PR