Problem
claude-yolo --trace . fails to add --dangerously-skip-permissions to the claude command, breaking YOLO mode's core functionality.
Root Cause
- In
claude.sh:559, when --trace is used, the command becomes claude-trace --include-all-requests --run-with
- In
docker-entrypoint.sh:167-169 (non-root) and 181-183 (root), the logic only adds --dangerously-skip-permissions when:
if [ "$cmd" = "claude" ] || [ "$cmd" = "$CLAUDE_CMD" ]; then
- Since
cmd is "claude-trace", it doesn't match this condition
Impact
YOLO mode loses its safety bypass when tracing is enabled, defeating the purpose of running in a container.
Reproduction
./claude-yolo --trace .
# Claude runs without --dangerously-skip-permissions, causing permission prompts
Solution Options
- Pattern matching: Check if command contains "claude" or ends with "claude-trace"
- Flag detection: Parse command args to detect if claude is being invoked regardless of wrapper
- Environment variable: Pass a flag to indicate YOLO mode should be active
Files Affected
claude.sh:559 (trace command construction)
docker-entrypoint.sh:167-169, 181-183 (permission logic)
See DEV-LOGS.md for detailed analysis.
Problem
claude-yolo --trace .fails to add--dangerously-skip-permissionsto the claude command, breaking YOLO mode's core functionality.Root Cause
claude.sh:559, when--traceis used, the command becomesclaude-trace --include-all-requests --run-withdocker-entrypoint.sh:167-169(non-root) and181-183(root), the logic only adds--dangerously-skip-permissionswhen:cmdis "claude-trace", it doesn't match this conditionImpact
YOLO mode loses its safety bypass when tracing is enabled, defeating the purpose of running in a container.
Reproduction
Solution Options
Files Affected
claude.sh:559(trace command construction)docker-entrypoint.sh:167-169, 181-183(permission logic)See DEV-LOGS.md for detailed analysis.