claude-code - 💡(How to fix) Fix Bash tool approval dialog: 'Unhandled node type: string' from tree-sitter bash renderer [1 comments, 2 participants]

When the Bash tool approval dialog renders a bash command containing certain syntax patterns, the tree-sitter bash syntax highlighter throws Unhandled node type: string. The error appears inline in the approval UI, requiring the user to acknowledge it before the command can proceed. The approval dialog renders the bash command with syntax highlighting (or no highlighting) without surfacing an error to the user. The dialog shows Unhandled node type: string as an error message that the user must acknowledge, creating repeated interruptions. Every time an agent runs a push-verify command pattern like the above, the user is prompted to address the error. In workflows where push verification runs frequently, this becomes persistent noise.

TL;DR

The issue can be mitigated by simplifying bash commands to avoid certain syntax patterns that trigger the Unhandled node type: string error in the tree-sitter bash syntax highlighter.

Guidance

• Identify and simplify bash commands that include single-quoted strings as command arguments, Unicode characters in double-quoted strings, or long multi-line commands chained with && and backslash continuation.
• Test commands without these patterns to verify if the error is resolved.
• Consider breaking down long commands into shorter, simpler ones to avoid triggering the error.
• If possible, avoid using Unicode characters in double-quoted strings or replace them with their ASCII equivalents.

Example

No code snippet is provided as the issue is related to the tree-sitter bash syntax highlighter and not a specific code error.

Notes

The provided workaround may not be feasible for all use cases, especially where complex bash commands are necessary. The root cause of the issue seems to be related to the tree-sitter-bash grammar not handling the string AST node in all positions.

Recommendation

Apply workaround: Simplify bash commands to avoid triggering syntax patterns, as this is a rendering-only bug and does not affect command execution. This approach can help mitigate the issue until a more permanent fix is available.