feat: Upwards-recursively read .env.braintrust containing BRAINTRUST_API_KEY on login in Node.js#2049
Merged
Merged
Conversation
…ST_API_KEY` on login in Node.js
Abhijeet Prasad (AbhiPrasad)
approved these changes
May 26, 2026
This was referenced May 26, 2026
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.
We are planning on a change where the wizard will generate a
.env.braintrustfile with aBRAINTRUST_API_KEYinto the cwd.This is so the user can use the wizard and immediately verify the generated instrumentation locally.
Some thoughts around this implementation:
.env.braintrust