Skip to content

Implement shell awareness feature for Q CLI #2521

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mibeco
Copy link
Contributor

@mibeco mibeco commented Aug 7, 2025

Description of changes:

  • Add unified shell detection system that works across tool creation, execution, and UI display
  • Support for zsh, bash, and other shells with fallback detection methods
  • Replace hardcoded 'execute_bash' references with dynamic shell-specific tool names
  • Add comprehensive documentation and testing instructions

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

- Add unified shell detection system that works across tool creation, execution, and UI display
- Support for zsh, bash, and other shells with fallback detection methods
- Replace hardcoded 'execute_bash' references with dynamic shell-specific tool names
- Add comprehensive documentation and testing instructions

## The Problem

The original Q CLI always showed `execute_bash` in the UI, regardless of what shell the user was actually running. This was misleading for users running zsh, fish, or other shells, as it suggested the tool wasn't aware of their shell environment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonder if we can get away by just changing it to execute_shell from execute_bash, usually Q won't do anything that is fish/zsh specific right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants