Problem
When Dippy encounters a command with a bash syntax error (e.g. unclosed quotes, broken continuations), it falls through to Decision("ask", ...) in analyzer.py:58-59. This means the user gets prompted for commands that are clearly broken and should just be rejected.
Suggestion
Add a config directive like:
on_parse_error deny "Syntax error — fix and retry."
with ask as the default for backwards compatibility. This would let users opt into auto-denying unparseable commands instead of being prompted.
Current workaround
Manually patching the hardcoded "ask" to "deny" in analyzer.py.
Context
In practice, syntax errors in AI-generated commands are never intentional — auto-deny with a descriptive message lets the AI agent self-correct without interrupting the user.
Problem
When Dippy encounters a command with a bash syntax error (e.g. unclosed quotes, broken continuations), it falls through to
Decision("ask", ...)inanalyzer.py:58-59. This means the user gets prompted for commands that are clearly broken and should just be rejected.Suggestion
Add a config directive like:
with
askas the default for backwards compatibility. This would let users opt into auto-denying unparseable commands instead of being prompted.Current workaround
Manually patching the hardcoded
"ask"to"deny"inanalyzer.py.Context
In practice, syntax errors in AI-generated commands are never intentional — auto-deny with a descriptive message lets the AI agent self-correct without interrupting the user.