wavetermdev / waveterm

An open-source, cross-platform terminal for seamless workflows
https://www.waveterm.dev
Apache License 2.0
3.75k stars 86 forks source link

Amazon-Q Integration Causes Initialization Failure in WaveTerminal #710

Open dmmeteo opened 1 month ago

dmmeteo commented 1 month ago

Describe the bug When launching WaveTerminal, there is a shell initialization error suggesting a conflict with the Amazon-Q shell scripts. The error occurs when the scripts zprofile.pre.zsh from the Amazon-Q integration are sourced during shell initialization, preventing WaveTerminal from starting properly. The error message displayed is: “error reinitializing remote: error initializing shell: invalid zsh shell state output, could not parse separator bytes.”

To Reproduce Steps to reproduce the behavior:

1.  Install WaveTerminal version 0.7.6 on Sonoma 14.5.
2.  Install Amazon-Q version 1.3.0 and configure its initialization scripts included in .zprofile and .zshrc.
3.  Open WaveTerminal.
4.  The aforementioned error appears, indicating a failure in shell initialization.

Expected behavior WaveTerminal should initialize without any errors, regardless of the shell scripts from other applications like Amazon-Q.

Screenshots If applicable, add screenshots to help explain the problem.

Desktop (please complete the following information):

•   OS: Sonoma 14.5
•   Version: WaveTerminal 0.7.6

Additional context The conflict arises from shell initialization scripts for Amazon-Q (version 1.3.0) that interfere with the shell environment expected by WaveTerminal. Temporarily resolving this issue involves commenting out the lines in .zprofile and .zshrc that source the Amazon-Q scripts. This indicates that these scripts alter the shell environment in a way that WaveTerminal cannot accommodate. A more permanent solution could be modifying the initialization order of these scripts, or WaveTerminal could potentially be updated to handle third-party shell configurations more robustly. By addressing the initialization sequence or managing environment isolation, WaveTerminal could avoid such conflicts and enhance compatibility with various shell enhancements.

Screenshot 2024-07-03 at 02 12 24
arhirani commented 1 month ago

I'm facing this issue as well. Apparently, I had to uninstall amazon-q to make it work.

dlanznar commented 1 month ago

I have the identical issue, also on Sonoma with latest WaveTerminal.

Commenting out the Amazon-Q pre/post script commands in bash/zsh dotfiles (also previous CodeWhisperer versions) did not help, but deleting Amazon-Q app does solve the problem.

saurabh-cimpress commented 1 month ago

I also have the same issue

ItielOlenick commented 3 weeks ago

Same here

xshapira commented 3 weeks ago

I'm in the same boat! Super frustrating.

chrisponton commented 1 week ago

Same here :(