fix: environment variables not available in VSCode Remote terminals#93
Merged
gricha merged 1 commit intogricha:mainfrom Jan 11, 2026
Merged
Conversation
VSCode Remote terminals do not inherit environment variables from PID 1, causing secrets like GITHUB_TOKEN to be unavailable. This broke git operations and other commands that rely on these credentials. Write environment variables to /etc/environment before starting sshd, using PAM's pam_env module to inject them into all session types. Credentials are synced both at container startup and when updated via the API. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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
Test plan