Summary
cmdLaunch() in LifeOS/install/LIFEOS/TOOLS/lifeos.ts (lines 424-426 on current main) documents a flag that does not exist:
// NOTE: We no longer use --dangerously-skip-permissions by default.
// The settings.json permission system (allow/deny/ask) provides proper security.
// Use --dangerous flag explicitly if you really need to skip all permission checks.
The argument parser in main() has no --dangerous case, and unknown flags are silently dropped (see #1690). So k --dangerous launches a completely normal session with standard permission checks.
Impact
The failure direction is safe (the user gets MORE permission enforcement than they asked for), but the file's own advice is wrong: anyone following that comment believes they changed permission behavior and did not.
Fix options
Either:
- implement the flag: parse
--dangerous and push --dangerously-skip-permissions onto the claude argv, or
- fix the comment to describe what actually exists.
Given the security-posture note in that same comment block, correcting the comment may be the better move; actually implementing a skip-permissions flag deserves a deliberate decision rather than a drive-by fix.
Related: #1690
Summary
cmdLaunch()inLifeOS/install/LIFEOS/TOOLS/lifeos.ts(lines 424-426 on currentmain) documents a flag that does not exist:The argument parser in
main()has no--dangerouscase, and unknown flags are silently dropped (see #1690). Sok --dangerouslaunches a completely normal session with standard permission checks.Impact
The failure direction is safe (the user gets MORE permission enforcement than they asked for), but the file's own advice is wrong: anyone following that comment believes they changed permission behavior and did not.
Fix options
Either:
--dangerousand push--dangerously-skip-permissionsonto the claude argv, orGiven the security-posture note in that same comment block, correcting the comment may be the better move; actually implementing a skip-permissions flag deserves a deliberate decision rather than a drive-by fix.
Related: #1690