Skip to content

docs(plz-3d-explain): clarify Python state persistence - #44

Open
Aaqibhafeezkhan wants to merge 1 commit into
codekongdev:mainfrom
Aaqibhafeezkhan:fix/issue-16-python-interpreter-state
Open

Aaqibhafeezkhan wants to merge 1 commit into
codekongdev:mainfrom
Aaqibhafeezkhan:fix/issue-16-python-interpreter-state

Conversation

@Aaqibhafeezkhan

Copy link
Copy Markdown

Changes

  • Clarify that sandbox reuse alone does not guarantee Python variable persistence.
  • Explain the distinction between filesystem state and Python interpreter memory.
  • State that starting a new Python process loses variables, even inside the same VM or container.
  • Explain how restoring a snapshot containing process memory can preserve interpreter state.
  • Align the Korean and English explanations, code comments and animation results.

Validation

  • Checked the lifecycle explanation in both languages.
  • Checked the example comments against the process-memory behavior.
  • Checked that the animation describes interpreter reuse and snapshot restoration consistently.

Closes #16

@coderabbitai

coderabbitai Bot commented Nov 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

Commits

Reviewing files that changed from the base of the PR and between 197d6d9 and 29df604.

Files selected for processing: 2

  • skills/plz-3d-explain/assets/example-agent-sandbox.en.html
  • skills/plz-3d-explain/assets/example-agent-sandbox.html

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@Aaqibhafeezkhan Aaqibhafeezkhan left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • The example now explicitly assumes the same Python interpreter across turns.
  • Files and variables have separate, clearly explained lifetimes.
  • Snapshot restoration is no longer presented as equivalent to simply reusing a sandbox.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[plz-3d-explain] Clarify when Python variables persist across sandbox reuse

1 participant