Repository navigation
Conversation
A client that reads /v1/models could not tell which endpoints teep refuses for a model while E2EE is enabled. The dashboard showed the coverage, but the model list did not. Each entry of the aggregated model list now has a `teep` member: the E2EE setting of the entry's provider in the running config (e2ee_enabled) and the endpoints that its E2EE covers and does not cover (e2ee_covers, e2ee_does_not_cover). The lists come from the same coverage declarations as the dashboard. With E2EE off both lists are empty, because teep then refuses no endpoint for coverage. Teep replaces a `teep` member that a provider sends, and sends no request to build the member. To verify: go test ./internal/proxy -run 'TestAnnotateModel|TestModelTeepMember|TestHandleModels'. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Problem
With E2EE enabled, teep refuses an endpoint that the provider's E2EE does not cover (see "Why teep refused my request" in
docs/api_support.md). The dashboard lists the covered and uncovered endpoints for each provider. A client that readsGET /v1/modelscannot see them, so it learns that an endpoint is refused only when it sends a request.Change
/v1/modelslist gets ateepmember:e2ee_enabled: the E2EE setting of the entry's provider in the running config.e2ee_coversande2ee_does_not_cover: the endpoint paths that the provider's E2EE covers and does not cover.e2eeCoverage, the same function the dashboard uses, which reads each encryptor'sCoversE2EEdeclaration. The change adds no new coverage logic, and no code path names a provider.teepmember that a provider sends, so only teep states the coverage.docs/api_support.mddescribes the member, with an example.Effect
A client can read from
/v1/modelswhich endpoints of a model teep sends with E2EE, and which ones it refuses while E2EE is enabled. Existing members of each entry do not change.To verify
TestModelTeepMemberchecks that the member holds the same lists as the dashboard for NearDirect with E2EE on, and empty lists with E2EE off.TestAnnotateModelchecks theidprefix and that an upstreamteepmember is replaced.TestHandleModelschecks the member throughGET /v1/models.Checklist
make checkpasses.make integrationandmake reportspass.