From ce0065fe8c2f149be8bf5802e669e0fc5befd468 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stig-=C3=98rjan=20Smelror?= Date: Fri, 6 Feb 2026 11:28:59 +0100 Subject: [PATCH] Clarify tool result limits apply only in local mode, add notes on unlimited incoming tool calls and dropped tool call detection --- src/pages/tools.astro | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/src/pages/tools.astro b/src/pages/tools.astro index 10a9293..732f014 100644 --- a/src/pages/tools.astro +++ b/src/pages/tools.astro @@ -824,19 +824,28 @@ import BaseLayout from '../layouts/BaseLayout.astro';

Tool Result Handling

-

Tool results are automatically truncated if they exceed limits:

+

The 50KB / 2000 line limits apply only to tool results — what zblade sends back to the model after executing a tool (e.g., the output of read_file). These limits only apply in local mode, when the Zaguán Coder Daemon isn't handling storage.

50KB - Max size + Result max size
2000 - Max lines + Result max lines

When truncated, the first 100 lines and last 50 lines are shown with a truncation message.

+ +
+

There are no size limits on incoming tool calls from the model. zblade will accept a write_file with any size content. The write_file handler itself has no caps — it writes whatever content string it receives directly to disk.

+
+ +
+ ℹī¸ +

zblade includes dropped tool call detection. If a tool call from the model never arrives (e.g., streaming progress events complete but the final tool call with arguments is dropped server-side), zblade will catch this and surface a clear error.

+