11 November: agent runs after a server update, and DeepSeek tool calls
After a server update, a running chat no longer acts as if it was just resumed at every step. Repeated tool names from DeepSeek on Featherless are repaired, and workflow summaries no longer split a call from its result.
People who run long tool chains, especially with DeepSeek models on Featherless: fewer repeated checks after a server update and fewer failed tool calls. No action needed.
After a server update. When ZeroLog is updated, a running chat moves to the other server and carries on. The model is told once that this happened, so it checks the state of its work before it goes on. Until now it was told again at every later step. It then announced that it was resuming, over and over, and checked the same files each time, which cost minutes on long runs. The note now goes out once.
Tool names sent twice. DeepSeek models on Featherless sometimes sent a tool's name several times in a row, such as run_command four times over. The call then failed as an unknown tool. When the name is an exact repetition of a tool offered in that step, the call now runs as intended. A repeated start of the arguments is trimmed only when that turns them into valid input.
Workflow summaries. The summary of an Ultracode workflow can arrive while the chat is in the middle of a tool step. In the history sent to the model it then sat between the call and its result, an order some providers reject. The history is now put in order before it is sent. What you see in the chat does not change.
No action is needed.