fix(cli): preserve voice transcript intent - #1
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.
Summary
Root cause
PR NousResearch#1299 (commit
a78249230) introduced an API-local prefix that forced voice replies to be conversational, limited them to 2–3 sentences, and prohibited Markdown/code blocks. That changes user intent solely because input came through STT and can truncate technical answers. The per-message sentinel added for NousResearch#65827 remains in place, so typed voice-control commands are still distinguishable from genuine STT output.Test plan
python -m pytest tests/cli/test_cli_interrupt_ack_race.py tests/tools/test_voice_cli_integration.py tests/run_agent/test_run_agent.py -o 'addopts=' -q_voice_prefixno longer existgit diff --check