Repository navigation
feat: enforce runtime guest output token limits - #25
Merged
Merged
Conversation
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.
Guest chat output limits are currently fixed by
GUEST_MAX_OUTPUT_TOKENSat startup. Readaccount.guest_max_output_tokensfrom Metering authentication so the limit saved in Admin → Settings → Guest chat applies to subsequent requests.The gateway uses the runtime value for both the provider request and its token reservation. It keeps the deployment fallback when older Metering responses omit the field; signed-in requests retain their existing behavior.
Validation:
go test ./apps/gateway/... ./pkg/...passes, including runtime-response mapping and output-limit tests above and below the deployment fallback.Deploy this gateway build before relying on runtime output limits in the companion Nexus settings change. It is compatible with the existing Metering response.
Companion admin settings PR: https://github.com/dappnode/dappnode-nexus/pull/163