feat: Use new eve instrumentation hooks - #2373
Merged
Merged
Conversation
Abhijeet Prasad (AbhiPrasad)
approved these changes
Aug 18, 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.
Based on vercel/eve#1799.
Upgrade guide
The instrumentation-provider API requires
eve@0.34.0or newer and the Braintrust release containing this PR (expectedbraintrust@3.28.0). After that release is published, upgrade both packages:Enable instrumentation providers on the Eve agent:
Then export the Braintrust provider directly from
instrumentation/braintrust.ts:With the provider API, do not wrap the result in Eve
defineInstrumentation, and do not pass EvedefineState. Remove the legacybraintrustEveHookconfiguration from root agents and subagents as well; the provider receives turn, model, and action lifecycle events for the entire trace and would otherwise duplicate instrumentation.Existing Eve integrations can remain on the legacy API. They may continue exporting
braintrustEveInstrumentation({ defineState, setup })until they are ready to upgrade Eve and enable instrumentation providers.