More than terminal commands
Claude Code sessions may contain shell commands, file reads and writes, pattern searches, web fetches, interactive questions, notebook edits, and delegated agent work. The viewer recognizes common tool names and derives a short human-readable summary from their input.
When a tool result exists, the details panel renders text, structured content, or supported images. Missing results are identified instead of being silently invented.
Useful for review and diagnosis
Tool visibility helps a reviewer distinguish a conclusion based on inspected evidence from one based on assumption. It also makes failed commands, partial results, and unexpected environment behavior part of the handoff.
- Verify which tests or build commands actually ran.
- Inspect the exact file path involved in a read or edit.
- Understand what a web search or delegated task was asked to do.
- Trace an error back to the command output that produced it.
Tool output may contain sensitive material
Command output and file contents are part of the transcript. Recognized credentials may be redacted by the skill, but filenames, source code, customer data, proprietary values, and arbitrary secrets can remain. Treat tool details as first-class content during review.