🧭 docs: Explain Code Environment Persistence - #775
Open
danny-avila wants to merge 1 commit into
Open
danny-avila wants to merge 1 commit into
danny-avila wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
10 of 15 tasks
Contributor
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This branch was successfully deployed
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
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
Code Interpreter documentation currently says installed packages and working state usually carry across Stateful Code Session runs. The implementation retains files but starts each execution in a fresh process, while attached workers have a different durable boundary: the selected registered workspace.
This update documents the actual lifecycle contract for managed stateless, managed stateful, and attached execution. It adds a backend comparison, practical handoff guidance, project-local dependency guidance, long-lived service ownership, and the worker-policy security boundary.
Companion implementation: LibreChat-AI/LibreChat#16099
Testing
Compatibility
Documentation only. It describes current behavior and does not require configuration or migration changes.