feat(evi): enable zero data retention on the gateway - #568
Merged
Conversation
|
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
4 Skipped Deployments
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
commit: |
HugoRCD
reviewed
Aug 12, 2026
HugoRCD
approved these changes
Aug 12, 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.
What
Enable zero data retention (ZDR) on every AI Gateway request made by the Evi agent by adding
zeroDataRetention: trueto the sharedgatewayRoutinginapps/evi/agent/lib/gateway.ts. Both model paths inagent.tsspread this routing, so all agent sessions route only through ZDR-compliant providers.Why
The agent's gateway traffic currently runs without ZDR (report grouping by
zero_data_retentionreturnsno-zdr-requestedfor all rows). Per-request ZDR is free on Pro/Enterprise. The default modeldeepseek/deepseek-v4-flashhas ZDR-compliant providers on AI Gateway, so this does not break routing.Notes
evals.config.ts) uses its own gateway options with only tags, so it is untouched by this change.apps/evi(internal agent), so no changeset is required.Checks
pnpm run lint: 22 tasks successful, exit 0pnpm --filter evi run typecheck: exit 0pnpm run test: 1811 tests / 87 files passedpnpm --filter evi exec vitest run agent/lib/gateway.test.ts: 4 passed (includes a new assertion thatgatewayRouting.zeroDataRetentionistrue)