Repository navigation
Show the Bash tool's description instead of the raw command in Claude work log rows #31650
HarryCarter1998
started this conversation in
Ideas
Replies: 1 comment
|
+1, I'd like this too. With recent Claude Code builds, searches go through Bash as well, so most of a Claude thread's work log ends up as raw shell commands, and I have to read The data is already there: Proposed scope:
If this direction and scope look OK to you, I'm happy to open a PR. Let me know if you'd rather have it behind a setting. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
What happens
On Claude threads, every shell tool call shows in the work log as its raw command, for example:
For everyday actions like searching for a keyword or listing a folder, you have to read a shell command to work out what the agent is doing. Claude Code's Bash tool already sends a short plain-English
descriptionwith each call, such as "Search Java sources for 'admin'", but T3 Code doesn't show it. In the thread activity,command_executionitems havetitle: null, andtextholds only$ <command>.Recent Claude Code builds have no separate Grep/Glob tools, so every search goes through Bash. Searches will always show as commands unless the description is surfaced. (File reads through the Read tool already show nicely as "Read ".)
Request
Use the Bash tool's
descriptionas the row label in the work log (and the activitytitle), with the full command still available when the row is expanded or hovered. Fall back to the command when there's no description.Possibly a setting: "Show command descriptions instead of raw commands".
Environment
All reactions