tool calls cannot be expanded to show details

[maphew]

Toad v0.58 on bluefin linux (atomic fedora).

The tool calls cannot be expanded to show what happened. Clicking on the right-triangle icon or the tool item line flashes the terminal title bar but there is no change in display.

I expected the triangle to point down and for the details of the tool call to show. If I hover just right a tool tip of the tool name will show, but that's it.

I tried changing the Setting 'Tool call expand' from 'Fail only' to 'Always' but it had no effect, even after restarting toad.

---

About Toad v0.5.8

© Will McGugan.

Toad is licensed under the terms of the GNU AFFERO GENERAL PUBLIC LICENSE.

Config

config read from /var/home/matt/.config/toad/toad.json

{
    "anon_id": "3ca30ef7-c7c4-4b56-bf7b-fe84774fe360", 
    "launcher": {
        "agents": "ampcode.com\nopenhands.dev"
    }, 
    "tools": {
        "expand": "always"
    }
}                       

Additional app data stored in /var/home/matt/.local/share/toad

System

System	Version
Python	CPython 3.14.0
OS	Linux-6.17.7-300.fc43.x86_64-x86_64-with-glibc2.42

Dependencies

Library	Version
Textual	6.11.0
Rich	14.2.0

Environment

Environment variable	Value
TERM	xterm-256color
COLORTERM	truecolor
TERM_PROGRAM
TERM_PROGRAM_VERSION

[willmcgugan]

The clock icon indicates it is still working. The arrow is greyed out which indicates there is not content to expand.

I can dim the arrow even further to make it clearer.

[maphew]

Oh that's a clue. The clock never goes away. I get the same behaviour when scrolling up backward through the conversation history.

[maphew]

Kilocode also has trouble detecting when a tool call has finished. Kilo is a vscode extension, and opens an embedded terminal in vscode for its tool calls. It will run a command like git status and sit there waiting for a long time even though the command finishes instantly. I've noticed that if I run a simple command like ls or pwd Kilo will quickly wake up and resume.

I've seen something similar with Windsurf on Windows. It's also a vscode extension so I've assumed it was a vscode problem, though now I'm wondering.

[tidux]

I'm seeing something similar with Toad 0.6.16 on MacOS 26. I click on this triangle but nothing happens. I press "x" and it appears in the prompt window. Is this functionality just broken? I know the tools ARE producing output because I can see the output in other ACP clients like agentic.nvim.

[willmcgugan]

If the tool has output it will expand. The arrow is faded out to show there is no output.

If you think that is an error, run with TOAD_LOG=acp.log and paste the log.

[KABoissonneault]

I'm having an issue similar to this discussion. I am running goose over a local agent. I don't currently have an isolated environment for my agent, so reviewing the exact details of tools like shell is critical to any operation. But from toad, I only see "shell" when it asks for my permission, clicking for full title only gives me an intent.

For example, I asked my agent to find which file in the project contained the word 'cheese'. While I could tell from its thinking that it was going to call greg or rg, toad only showed me "shell" then "Searching for 'cheese'" when expanded.

For reference, the same setup on VS Code shows me this:

From the TOAD_LOG,

[agent] {"jsonrpc":"2.0","method":"session/update","params":{"sessionId":"20260628_2","update":{"sessionUpdate":"agent_thought_chunk","content":{"type":"text","text":"cheese"},"_meta":{"goose":{"created":1782684096,"messageId":"chatcmpl-bBIHTUJdhRERrkWT7SY0OyMXWQ1s7QyL"}}}}}
[agent] {"jsonrpc":"2.0","method":"session/update","params":{"sessionId":"20260628_2","update":{"sessionUpdate":"agent_thought_chunk","content":{"type":"text","text":"\"."},"_meta":{"goose":{"created":1782684096,"messageId":"chatcmpl-bBIHTUJdhRERrkWT7SY0OyMXWQ1s7QyL"}}}}}
[agent] {"jsonrpc":"2.0","method":"session/update","params":{"sessionId":"20260628_2","update":{"sessionUpdate":"tool_call","toolCallId":"zbb3asehi3bZaeD2Vb6fPbrT0WD5RPrx","title":"shell · rg \"cheese\"","rawInput":{"command":"rg \"cheese\""},"_meta":{"goose":{"toolCall":{"toolName":"shell","extensionName":"developer"}}}}}}
[agent] {"jsonrpc":"2.0","method":"session/request_permission","params":{"sessionId":"20260628_2","toolCall":{"toolCallId":"zbb3asehi3bZaeD2Vb6fPbrT0WD5RPrx","kind":"other","status":"pending","title":"shell","rawInput":{"command":"rg \"cheese\""}},"options":[{"optionId":"allow_always","name":"allow_always","kind":"allow_always"},{"optionId":"allow_once","name":"allow_once","kind":"allow_once"},{"optionId":"reject_once","name":"reject_once","kind":"reject_once"},{"optionId":"reject_always","name":"reject_always","kind":"reject_always"}]},"id":"e8d2aa3d-4d3c-413d-8ee7-7ae4e3e085db"}
[agent] {"jsonrpc":"2.0","method":"session/update","params":{"sessionId":"20260628_2","update":{"sessionUpdate":"tool_call_update","toolCallId":"zbb3asehi3bZaeD2Vb6fPbrT0WD5RPrx","title":"searching for cheese","_meta":{"goose":{"toolCall":{"toolName":"shell","extensionName":"developer"}}}}}}
[agent] {"jsonrpc":"2.0","method":"session/update","params":{"sessionId":"20260628_2","update":{"sessionUpdate":"session_info_update","title":"Searching for 'cheese'","updatedAt":"2026-06-28T22:01:48+00:00","_meta":{"messageCount":1,"userSetName":false}}}}

It seems like there is a tool_call session update providing the title of the tool call, followed by a request_permission containing the simple "shell" title. We also see the tool_call_update at the end that changes the title to "searching for cheese".

I'm not familiar with the expected behavior from ACP, but it seems like other clients support specifying a tool_call title before the permission request, and render that title instead. If goose is in the wrong, I can open an issue there instead

[lifeizhou-ap]

Hi @KABoissonneault!

Thanks for the detailed report and logs. We’ve updated Goose so the initial tool call and permission request use the same deterministic title. In your example, both will show something like shell · rg "cheese" instead of the permission request showing only shell.

Toad does not need to enable LLM-generated label enrichment, so it will keep the consistent command-based title without additional model calls.

The title consistency fix merged in goose#10599, with capability gating being completed in goose#10644.