Forward unknown arguments to `claude` (e.g. --dangerously-skip-permissions, -p, -c)

[ydemir]

Summary

The deepclaude wrapper currently rejects any flag that isn't part of its own CLI surface. As a result, native Claude Code flags — including --dangerously-skip-permissions, --permission-mode, -p, -c, -r, --model, --add-dir — can't be passed through.

The README describes the project as "swaps the brain while keeping the body," but right now the body's flags don't reach claude.

Reproduction

PowerShell on Windows 11, latest main:

PS> deepclaude --dangerously-skip-permissions
ERROR: Unknown backend '--dangerously-skip-permissions'. Use: ds, or, fw, anthropic

Same for any other Claude Code flag:

PS> deepclaude -p "explain this repo"
ERROR: Unknown backend '-p'. Use: ds, or, fw, anthropic

PS> deepclaude -c
ERROR: Unknown backend '-c'. Use: ds, or, fw, anthropic

Expected behavior

Unknown arguments should be forwarded as-is to the underlying claude invocation. Backend selection should compose with native flags, so all of these should work:

[aattaran]

Confirmed PowerShell-only bug — bash side already works (the parser hits *) break ;; and remaining args stay in "$@" which gets passed to claude). PowerShell's strict param() block absorbs unrecognized dashed flags into $Backend via positional/prefix matching, which is what produces the Unknown backend '--dangerously-skip-permissions' error.

Fix: add [Parameter(ValueFromRemainingArguments=$true)] [object[]]$ClaudeArgs to the param block and replace the four @Args invocation sites with @ClaudeArgs. Tested locally — deepclaude --dangerously-skip-permissions, deepclaude -p "explain", deepclaude -c all forward correctly to claude after the fix.

Will land in a follow-up commit.