Repository navigation
docs(models): update reasoning-only stream limit to input-aware bounds - #143
Merged
Merged
Conversation
The published numbers (60,000 characters / ~44,000 measured ceiling) are stale after the 2026-10-02 watchdog tune: the seconds bound is now 420s (600s past 45,000 reasoning characters) and the character budget scales with prompt size (150,000 + half the prompt, capped at 300,000).
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.
What
Updates the public "Reasoning-only stream limit" section (EN + ES) to match the deployed watchdog behavior after the 2026-10-02 tune (nan-devops commit ec88bc24, pending PR):
Why
The published numbers no longer match the platform; members quote them when reporting cuts.
Test evidence
npm run buildPASS (Astro build, adapter Cloudflare). Usage-chunk paragraph and guidance bullets unchanged (still accurate).Deploy notes
Deploys automatically on merge via Cloudflare Pages (push to main). Merge after the nan-devops watchdog PR lands so docs never describe behavior ahead of the deploy.