Comment by bob1029
6 hours ago
> Fourth, if long tool-calling turns still go quiet for longer than you want, have your harness ask for an update
I'm not sure I understand this complexity. In all harnesses I've ever used, tool calls themselves are surfaced to the user as an indication of progress. When the UI/UX around this is engineered well, the user should be able to infer roughly what is going on. Different tools have different ideal presentations. You can't reduce everything to plaintext blobs.
If I absolutely needed intra-turn progress updates, I'd accumulate a separate per-turn transcript and feed it into a cheaper model at deterministic intervals.
Claude code has been hiding tool calls for some months now :(
How does it hide tool calls? I have to run those and return the results.
Are you in manual approval mode? That's the only way I can imagine you have to "run" tools yourself.
In Auto Mode, it's common to see something like "Called bash, called MCPImageEditor 7 times" with no further details, not even the parameters that were passed or specific functions/tools that were called.
[dead]