You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description
When running the program, the terminal output is not well formed. When comparing to the output of running it in a separate bash session, it looks wrong. Terminal output should be correctly formatted. This output consists of three lines. The three lines are there, but they are offset incorrectly so that the columns do not align.
@igorkofman I do not have permission to re-open the issue, but the problem is still there. I think it is related to Claude using Bash. Read() works as in your example. Claude using Bash does not work. Directly executing commands with exclamation mark does not work:
I believe Claude removes initial spaces from Bash output.
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.
Activity
igorkofman commentedon Mar 6, 2025
Cannot repro this with the latest version in Apple Terminal
Please re-open if this issue persists.
ekenberg commentedon Mar 6, 2025
@igorkofman I do not have permission to re-open the issue, but the problem is still there. I think it is related to Claude using Bash. Read() works as in your example. Claude using Bash does not work. Directly executing commands with exclamation mark does not work:
I believe Claude removes initial spaces from Bash output.
igorkofman commentedon Mar 6, 2025
Thanks - we'll dig in!
igorkofman commentedon Mar 7, 2025
Should be fixed in the next version (Monday)
ekenberg commentedon Mar 18, 2025
Update FYI: problem still persists in
v0.2.48igorkofman commentedon Mar 18, 2025
Oh man, this regressed. Fixing and adding tests :)
igorkofman commentedon Mar 18, 2025
(pass) BashTool output > preserves leading whitespace in output - should be fixed permanently tomorrow.
github-actions commentedon Aug 9, 2025
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.