fix(cli): correct bash syntax in terminal integration functions#6181
Merged
blackgirlbytes merged 1 commit intoblock:mainfrom Dec 23, 2025
Merged
Conversation
Fixed bash syntax error by changing double curly braces to single
curly braces in function definitions for bash and zsh terminal
integration. The double braces were being output literally, causing
'syntax error near unexpected token' errors.
Changes:
- goose_preexec() function definitions in BASH_CONFIG and ZSH_CONFIG
- command_not_found_handle/handler() function definitions
Fixes the error:
bash: eval: line 100: syntax error near unexpected token '{{'
bash: eval: line 100: 'goose_preexec() {{'
Signed-off-by: Josh Noll <noll.joshua@outlook.com>
katzdave
approved these changes
Dec 19, 2025
Contributor
|
amazing, and it got approved. I'm going to merge it. |
wpfleger96
added a commit
that referenced
this pull request
Dec 23, 2025
* main: (155 commits) remove Tool Selection Strategy preview (#6250) fix(cli): correct bash syntax in terminal integration functions (#6181) fix : opening a session to view it modifies session history order in desktop (#6156) test: fix recipe and audio tests to avoid side effects (#6231) chore: Update gemini versions in test_providers.sh (#6246) feat: option to stream json - jsonl really (#6228) feat: add mcp app renderer (#6095) docs: update skills extension to support .agents/skills directories (#6199) Add YouTube short to Chrome DevTools MCP tutorial (#6244) docs: Caveats for privacy information in logs documentation (#6218) move goose issue solver to opus (#6233) feat: improved UX for tool calls via execute_code (#6205) Blog: Code Mode Doesn't Replace MCP (#6227) fix: prevent keychain requests during cargo test (#6219) test: fix test_max_turns_limit slow execution and wrong message type (#6221) Skills vs MCP blog (#6220) Add blog post: Does Your AI Agent Need a Plan? (#6209) fix(ui): enable MCP UI to send a prompt message when an element is clicked (#6207) docs: param option for recipe deeplink/open (#6206) docs: edit in place or fork session (#6203) ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixed bash syntax error by changing double curly braces to single curly braces in function definitions for bash and zsh terminal integration. The double braces were being output literally, causing 'syntax error near unexpected token' errors.
Changes:
Fixes the error:
bash: eval: line 100: syntax error near unexpected token '{{' bash: eval: line 100: 'goose_preexec() {{'
Summary
Type of Change
AI Assistance
Testing
Related Issues
Relates to #6142
Discussion: #6142 (comment)
Screenshots/Demos (for UX changes)
Before:
After: