Conversation
- Explain automatic cleanup of merged worktrees and leftover processes - Require sharing a pairing URL for manual web verification
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.
What Changed
Removed shell-specific startup wrappers for Bash and zsh virtual environment activation. T3 Code now activates detected Python environments directly through the terminal process and retains the existing success/failure marker handling. Updated terminal tests and user documentation accordingly, and documented the worktree verification handoff workflow.
Why
The startup wrappers added substantial complexity and temporary-file lifecycle management for behavior that can be handled by a direct activation command. Simplifying the flow makes activation more reliable across shells while preserving automatic environment discovery and concise failure reporting.
Checklist