Summary
Related: livekit-agents#6109
Issue #6109 adds item_id to UserInputTranscribedEvent so consumers can correlate interim and final transcription updates belonging to the same user utterance.
However, the remote session transport currently serializes UserInputTranscribed through protobuf, and the protobuf message does not contain an item_id field. As a result, even after the event API exposes item_id, remote session consumers will still not receive it.
This creates inconsistent behavior between local and remote deployments.
Proposed Change
Add an item_id field to the UserInputTranscribed protobuf message and propagate it through the remote session transport.
Example:
message UserInputTranscribed {
string transcript = 1;
bool is_final = 2;
string item_id = 3;
}
(Exact field numbering/type can follow repository conventions.)
Summary
Related: livekit-agents#6109
Issue #6109 adds item_id to UserInputTranscribedEvent so consumers can correlate interim and final transcription updates belonging to the same user utterance.
However, the remote session transport currently serializes UserInputTranscribed through protobuf, and the protobuf message does not contain an item_id field. As a result, even after the event API exposes item_id, remote session consumers will still not receive it.
This creates inconsistent behavior between local and remote deployments.
Proposed Change
Add an item_id field to the UserInputTranscribed protobuf message and propagate it through the remote session transport.
Example:
message UserInputTranscribed {
string transcript = 1;
bool is_final = 2;
string item_id = 3;
}
(Exact field numbering/type can follow repository conventions.)