Repository navigation
docs: correct custom endpointing rule precedence - #1325
Merged
stephenvapiai merged 2 commits intoOct 14, 2026
Merged
Conversation
Transcriber end-of-turn detection is used before custom rules are evaluated when no smartEndpointingPlan is set or its provider is the transcriber. Custom rules win over smart and heuristic endpointing but not over transcriber end-of-turn, so 'highest priority' was wrong.
chiranjeet-vapi
force-pushed
the
docs/endpointing-precedence
branch
from
October 14, 2026 04:09
d86825b to
567dfae
Compare
chiranjeet-vapi
marked this pull request as ready for review
October 14, 2026 16:42
Lightsage docs evalsWaiting for the staging docs URL before running evals. Lightsage will start the selected PR evals automatically when GitHub reports a successful docs deployment for this PR. This usually happens within 15 minutes. Commit: |
stephenvapiai
approved these changes
Oct 14, 2026
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
2 participants
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.
Description
fern/customization/voice-pipeline-configuration.mdxlists the endpointing order as transcriber EOT, then custom rules, then smart endpointing, while also calling custom rules "highest priority" and saying they "override all other endpointing decisions". Both can't be true, and the second is wrong.transcriptionEndpointingPlan, not transcriber end-of-turn.Evidence
smartEndpointingPlanis set or its provider is the transcriber itself, and custom rules are evaluated only when it is not.Testing Steps
fern check(pinned 5.151.1) passes locally