feat: way to view output from tool calls / commands

[maria-rcks]

[rozatoo]

Extra context/Ideas:

• Easily switch between display output vs collapse output by default
• Color based on success or failed exit code?
• View output in full screen? (Nice for really long outputs like tofu plan)
• Maybe a way to have it auto-expand on only commands that require approval?

[HabsaTheDog]

Yes this is also good to understand if there is a wrong tooluse or broken commands the Agent is using.

[aashishsingla567]

Also, some observability on the Subagents spawned by Codex etc. would be great. They are also invisible right now.

[jeroenev]

Yeah, visibility should be improved for both subagents and tool calls.
I was hoping that T3code would have better visibility now that OpenCode is no longer allowed to use Anthropic Subs (Opencode does this best imho, especially for subagents)

[Quicksaver]

Related with usable code/references:

• Expandable File Change and Command activity boxes #3005
• Subagent support as nested threads #538 (comment)

[juliusmarminge]

PR #4083 has been refreshed without opening a new PR: branch codex/refresh-pr-4083 at commit bf58a964cd. The echoed-command/output defect is covered by 62 focused tests and real-app before/after evidence. Status remains 🚧 In Progress until merge.

[prom3theu5]

Any ideas when this will be in - im one of the sadists that likes to run claude desktop in verbose mode - i like to see whats occurring on all tool calls :)

[ineffyble]

This is my main blocker, want to be able to use T3 day-to-day but not being able to actually see the outputs of commands is too limiting.

[ben-vargas]

Yeah, +1 on this... I do a lot of work with custom CLIs connecting to enterprise software. Without being able to see the full bash tool calls and their outputs, I really can't rely on T3 for day to day "day job" work. I need to know when a bash/shell tool call doesn't behave as expected or needs optimization, T3 obfuscates that all.

I get that this was probably a design decision to keep things "friendly" and "simple" for the vibe coder initially, but an advanced option to show the outputs is very much required for adoption.

[mikenrafter]

Throwing my hat into the ring... I also greatly desire visibility. Frankly the only reason I'm using T3 in spite of this glaring oversight is its wonderful session management and remote-use combined with subscription-account compatibility.