Problem
Claude Code 1.0.0 removed the --disable-slash-commands CLI flag as a breaking change. The gh-aw compiler unconditionally injects this flag when building Claude engine execution steps, causing all Claude-engine workflows to fail at runtime with:
error: unknown option '--disable-slash-commands'
This results in the generic error:
ERR_CONFIG: Claude execution failed: no structured log entries were produced.
This usually indicates a startup or configuration error before tool execution.
Evidence
Affected Code
pkg/workflow/claude_engine.go:116 — unconditionally appends --disable-slash-commands to Claude CLI args
pkg/workflow/claude_engine_test.go:106-107 — asserts the flag is present
pkg/workflow/testdata/TestWasmGolden_CompileFixtures/claude-with-network.golden — golden test file contains the flag
- 43
.lock.yml files — all compiled Claude workflows contain the flag
Solution
- Remove line 116 from
pkg/workflow/claude_engine.go (the --disable-slash-commands append)
- Update the test in
claude_engine_test.go to no longer assert the flag is present
- Update the golden test file
claude-with-network.golden
- Run
make recompile to regenerate all 43 affected .lock.yml files
- Run
make agent-finish to validate
Notes
- The
--disable-slash-commands flag was originally added to prevent slash command injection during automated execution. Since Claude Code 1.0.0 removed it, slash commands may now be interpreted. Consider whether alternative mitigation is needed (e.g., input sanitization or a Claude settings file option).
- The NPM package
@anthropic-ai/claude-code is also deprecated in favor of native installers — that is a separate concern tracked elsewhere.
Problem
Claude Code 1.0.0 removed the
--disable-slash-commandsCLI flag as a breaking change. The gh-aw compiler unconditionally injects this flag when building Claude engine execution steps, causing all Claude-engine workflows to fail at runtime with:This results in the generic error:
Evidence
error: unknown option '--disable-slash-commands')--disable-slash-commandsremoved in 1.0.0 (CHANGELOG)Affected Code
pkg/workflow/claude_engine.go:116— unconditionally appends--disable-slash-commandsto Claude CLI argspkg/workflow/claude_engine_test.go:106-107— asserts the flag is presentpkg/workflow/testdata/TestWasmGolden_CompileFixtures/claude-with-network.golden— golden test file contains the flag.lock.ymlfiles — all compiled Claude workflows contain the flagSolution
pkg/workflow/claude_engine.go(the--disable-slash-commandsappend)claude_engine_test.goto no longer assert the flag is presentclaude-with-network.goldenmake recompileto regenerate all 43 affected.lock.ymlfilesmake agent-finishto validateNotes
--disable-slash-commandsflag was originally added to prevent slash command injection during automated execution. Since Claude Code 1.0.0 removed it, slash commands may now be interpreted. Consider whether alternative mitigation is needed (e.g., input sanitization or a Claude settings file option).@anthropic-ai/claude-codeis also deprecated in favor of native installers — that is a separate concern tracked elsewhere.