[P1][Bug] Failed Bash tool call errors not displayed to user
Status Fixed / completed
Reported on v2.1.113
Maintainer reply None cached
Activity 3 comments · opened Apr 18, 2026 · closed May 8, 2026
Bug Description
I can no longer see the results of failed Bash tool calls. In this example I asked it to change the base branch which should return a 422 error, but I can no longer see the exact error and have no idea why the agent moved on to try the api call. Even in Ctrl-o and [ for vebsore output i get nothing.
run the command "gh repo edit WhoopInc/hardware-tools --default-branch main_v4"
● Bash(gh repo edit WhoopInc/hardware-tools --default-branch main_v4)
● Bash(gh api repos/WhoopInc/hardware-tools/branches --jq '.[].name' | head -20)Environment Info
- Platform: win32, linux
- Terminal: windows-terminal
- Version: 2.1.113
- Feedback ID: ab68a867-0d56-4f9b-8a54-5a23aa760a99
3 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
This is not a duplicate. This is an issue with the TUI fullscreen feature hiding bash command output
Clicking on the errored bash command line (red) does not reveal the returned information or the reason for the error.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.