feat(agent): split k3 profile context windows — k3 1M, k3-256k 256K - #125
Merged
Conversation
Longest-prefix matching gives k3-256k its own 256K entry while bare k3 keeps the 1M context window. Timeout stays 300s for both.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
odek | ab1698c | Commit Preview URL Branch Preview URL |
Jul 29 2026, 09:43 AM |
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
1 participant
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
The
k3profile introduced in #124 assigned a single 256K context fallback to the whole family, but the variants differ: barek3has a 1M context window,k3-256kis the 256K variant.Changes
odek.go— separateKnownProfilesentries:k3-256k→ 256K,k3→ 1M. Existing longest-prefix matching resolvesk3-256kto its own entry before thek3prefix. Timeout stays 300s for both;/modelsdiscovery still takes priority over these fallbacks.docs/PROVIDERS.md—k3andk3-256klisted as separate rows.Test coverage
TestLookupProfile_KimiMatchnow assertsk3→ 1M andk3-256k→ 256K.TestNew_SideCallTimeoutScalingstill passes unchanged (both variants keep the 300s timeout → 120s capped side-call bound).go build ./...and the profile tests pass.