From 2a4ff3d656d87f05ae673c6ad412e8f008eb3571 Mon Sep 17 00:00:00 2001 From: Sergey Kozyrenko Date: Fri, 19 Jun 2026 04:32:50 +0700 Subject: [PATCH] docs: fix false tool-call attribution in parser troubleshooting (#330) The "failed to select primary docker image via llm call" symptom was attributed to tool-call parser failures, but image selection is a plain text completion (providers.go: prv.Call -> WrapGenerateFromSinglePrompt), not a tool call. That error is a generic LLM-backend failure of the `simple` agent type and is already covered in its own README section. Co-Authored-By: Claude Opus 4.8 --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 6b6adc02..3af17d0f 100644 --- a/README.md +++ b/README.md @@ -1403,7 +1403,6 @@ Typical symptoms: - Backend or proxy errors such as `Failed to parse tool call arguments as JSON` (often surfaced through a LiteLLM proxy as an HTTP 500), or other unexpected 5xx/4xx responses from the LLM endpoint. - A flow that runs for a few steps and then stops responding to new input in the UI. - Repeated or looping tool calls that never converge. -- A flow that fails right at the start with `failed to select primary docker image via llm call`, because the first action in a flow is an LLM tool call to choose the container image; a backend that cannot return a valid tool call fails at this step too. How to investigate: