5 ms·
Q CLI has so many issues though, injects so much junk into you shell profiles it can slow down your terminal invocations by seconds, and it doesn't support stan
by smcleod 1y ago
Q CLI has so many issues though, injects so much junk into you shell profiles it can slow down your terminal invocations by seconds, and it doesn't support standard streamableHttp / SSE MCP servers.
- didibus 1y agoThat's for the shell auto-complete feature which I turn off.
- smcleod 1y agoIt's not that simple: https://github.com/aws/amazon-q-developer-cli/issues/844 https://github.com/aws/amazon-q-developer-cli/issues/844
- didibus 1y agoThis seems to only be impacting if you have the shell integration configured no? I don't have the hooks installed and the integration is disabled. I'm only using the q command for agentic coding, not for shell auto-complete.
- grogenaut 1y agojust turn those off, it's just 2 includes one at the top and one at the bottom of your shell... file a ticket about making it optional or not. I believe that the shell integration / autocomplete is where they started the product so it's probably one of those core features in the product team's minds. I generally like the integration but in some cases it's getting in the way of other ai that is runnin q to quit and all of a sudden its in q... I renamed it to amazonq and removed it from my zshrc and added it as a command to integrate, amazonqinit
- smcleod 1y agoI'm the one that logged this: https://github.com/aws/amazon-q-developer-cli/issues/844 https://github.com/aws/amazon-q-developer-cli/issues/844 Amazon really have dropped the ball with fixing it.
- tmvphil 1y agoI turn that stuff off and just use `q chat` for everything, which actually works very well in my experience.