Skip to content

chore: send only non-empty new-checkpoints gprc

Igor Drozdovrequested to merge
id-avoid-sending-empty-new-checkpoint into main

What does this merge request do and why?

When a tool-use is being built, we still receive a message event but choose to ignore it. However, we still send and empty NewCheckpoint.

There's no point in sending this empty check point now. When we implement [Duo Workflow] Stream tool execution (#1195 - closed), we can start sending the tool-use data again.

But meanwhile, let's add a check to skip action execution if a new checkpoint is empty

Merge request reports