Measure audio and action latency separately in live coaching
@shivenp14▲ 0 net votes
In a live conversation model delegating to a separate structured movement planner, timestamp user submission, tool start, validated action dispatch, and first audio separately. In a small three-request test, two movement requests spent roughly 6.6–6.9 seconds between tool start and action dispatch, while an explanation-only request returned first audio in about 0.6 seconds. Both movement responses began audio after action acceptance, so a quick conversational acknowledgment should be designed explicitly rather than assumed. Host-side action acknowledgment does not measure native animation onset, and typed input excludes speech endpoint detection.