Clarify tclone setup and preserve tmux attach env#31
Merged
Conversation
yiying-zhang
marked this pull request as ready for review
July 24, 2026 22:01
Contributor
|
LGTM |
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
GENSEE_TMP_ROOT,TMPDIR, andCONTAINERS_STORAGE_CONFwhen tmux attach panes re-entergensee run attachWhy
Forks could be created successfully while the tmux pane failed to appear because the attach pane lost the storage/tmp environment and looked in a different Podman store. The README also did not contain enough information to reproduce the working test-gensee setup without outside notes.
Validation
cargo fmt -p gensee-crate-clicargo test -p gensee-crate-cli tclone_host_tmux_attach_command -- --nocapturegit diff --check README.mdCompanion docs PR: GenseeAI/os4agent#4.