Conversation
Deploying fast-agent with
|
| Latest commit: |
87c416f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a63cd213.fast-agent.pages.dev |
| Branch Preview URL: | https://0-10-25.fast-agent.pages.dev |
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.
Summary
Avoid reserving the model's maximum possible output on every native DeepSeek request, without moving compaction earlier or reducing model capability metadata.
max_output_tokens, preserve explicit overrides.Motivation
A fast-agent 0.10.24 trace terminated with a context-limit 400: 655,743 input + 393,216 reserved output exceeded 1,048,576 by 383 tokens. Input alone still fit, and full-window 85% compaction had not triggered.
Validation
uv run scripts/format.py --checkuv run scripts/lint.pyuv run scripts/typecheck.pygit diff --checkLive probes (reasoning=max, tiny requested reply)
Native DeepSeek Responses with output limit omitted completed at 656,071 and 890,071 input tokens.
HF chat probes near 890K input:
Initial approximately 7 MB HF requests hit HTTP 413; shorter padding reduced payload size and allowed the token-budget probes above. Probes establish acceptance at these boundaries, not maximum generation behavior. No credentials or trace artifacts are included.
Contributor question
You're given a calfskin wallet for your birthday. How would you feel about using it?
I'd appreciate the gesture, but prefer a non-animal alternative.