Skip to content

feat(evi): enable zero data retention on the gateway - #568

Merged
HugoRCD merged 2 commits into
mainfrom
chore/evi-zero-data-retention
Aug 12, 2026
Merged

feat(evi): enable zero data retention on the gateway#568
HugoRCD merged 2 commits into
mainfrom
chore/evi-zero-data-retention

Conversation

@evlogai

@evlogai evlogai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

What

Enable zero data retention (ZDR) on every AI Gateway request made by the Evi agent by adding zeroDataRetention: true to the shared gatewayRouting in apps/evi/agent/lib/gateway.ts. Both model paths in agent.ts spread 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_retention returns no-zdr-requested for all rows). Per-request ZDR is free on Pro/Enterprise. The default model deepseek/deepseek-v4-flash has ZDR-compliant providers on AI Gateway, so this does not break routing.

Notes

  • ZDR skips BYOK keys by default and fails closed: if a model has no ZDR-compliant provider the request errors rather than silently downgrading. The default and eval models both have ZDR coverage today.
  • The eval judge (evals.config.ts) uses its own gateway options with only tags, so it is untouched by this change.
  • The change is confined to apps/evi (internal agent), so no changeset is required.

Checks

  • pnpm run lint: 22 tasks successful, exit 0
  • pnpm --filter evi run typecheck: exit 0
  • pnpm run test: 1811 tests / 87 files passed
  • pnpm --filter evi exec vitest run agent/lib/gateway.test.ts: 4 passed (includes a new assertion that gatewayRouting.zeroDataRetention is true)

@changeset-bot

changeset-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 6e5a2b2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@evlogai
evlogai Bot requested a review from HugoRCD August 12, 2026 16:06
@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
evi Ready Ready Preview Aug 12, 2026 4:45pm
4 Skipped Deployments
Project Deployment Actions Updated (UTC)
evlog-docs Skipped Skipped Aug 12, 2026 4:45pm
evlog-render-lab Skipped Skipped Aug 12, 2026 4:45pm
evlog-telemetry Skipped Skipped Aug 12, 2026 4:45pm
just-use-evlog Skipped Skipped Aug 12, 2026 4:45pm

Request Review

@github-actions

Copy link
Copy Markdown
Contributor

Thank you for following the naming conventions! 🙏

@pkg-pr-new

pkg-pr-new Bot commented Aug 12, 2026

Copy link
Copy Markdown
npm i https://pkg.pr.new/@evlog/cli@568
npm i https://pkg.pr.new/evlog@568
npm i https://pkg.pr.new/@evlog/nuxthub@568
npm i https://pkg.pr.new/@evlog/telemetry@568

commit: 4b7dc1c

Comment thread apps/evi/agent/lib/gateway.ts
@vercel
vercel Bot temporarily deployed to Preview – just-use-evlog August 12, 2026 16:44 Inactive
@vercel
vercel Bot temporarily deployed to Preview – evlog-docs August 12, 2026 16:44 Inactive
@vercel
vercel Bot temporarily deployed to Preview – evlog-render-lab August 12, 2026 16:44 Inactive
@vercel
vercel Bot temporarily deployed to Preview – evlog-telemetry August 12, 2026 16:44 Inactive
@HugoRCD
HugoRCD merged commit 78262bf into main Aug 12, 2026
15 of 16 checks passed
@HugoRCD
HugoRCD deleted the chore/evi-zero-data-retention branch August 12, 2026 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant