Session resume does not preserve --dangerously-skip-permissions flag

Description

When resuming a session (via /continue or selecting from the session list), Claude Code spawns a new process without preserving the --dangerously-skip-permissions flag from the original invocation.

Steps to Reproduce

1. Start Claude Code with the flag:

``bash
claude --dangerously-skip-permissions
``

1. Work in the session, then exit (Ctrl+C or close terminal)
2. Resume the session (via /continue or session picker)
3. Check if permissions are still being skipped - they are not

Evidence

Multiple Claude processes running, showing the discrepancy:

PID 2400013 (Jan27) - claude --dangerously-skip-permissions  # original
PID 3665966 (09:58) - claude                                  # resumed session

The resumed process cmdline from /proc/3665966/cmdline shows just claude with no flag.

Session timeline confirms resume:

• Session directory created: Jan 30 01:39 (with flag)
• Current process started: Jan 30 09:58 (without flag)

Expected Behavior

The --dangerously-skip-permissions flag should be persisted with the session metadata and restored when the session is resumed.

Environment

• Claude Code version: 2.1.25
• OS: Linux (Ubuntu)
• Installation: ~/.local/bin/claude -> ~/.local/share/claude/versions/2.1.25

Workaround

Restart Claude with the flag instead of resuming:

claude --dangerously-skip-permissions