Quick fix for hot-reload of .env#1
Open
pelted wants to merge 1 commit into
Open
Conversation
…dling and actually make it hot-reload per the README
jbeker
approved these changes
Feb 27, 2026
Collaborator
jbeker
left a comment
There was a problem hiding this comment.
Will be curious to see how that works with using the 1P .env support. If it starts prompting us to auth for every tool call. But worth a shot :)
Contributor
Author
|
Oh that is a good point. Umm, I was trying to fuddle with my env when I ran into it not reloading, but now that may be an issue if it prompts. I'll wait on merging until I can verify |
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.
load_dotenv(override=True)runs once during__init__, so any .env changes after startup are invisible. The fix is to move that call into_get_headersso it re-reads the file on every request.