Skip to content

feat: add persistent yolo mode setting - #374

Closed
alecuba16 wants to merge 1 commit into
Kuberwastaken:mainfrom
alecuba16:feat/yolo-mode
Closed

feat: add persistent yolo mode setting#374
alecuba16 wants to merge 1 commit into
Kuberwastaken:mainfrom
alecuba16:feat/yolo-mode

Conversation

@alecuba16

Copy link
Copy Markdown

Summary

Adds persistent YOLO mode (auto-approve all tool calls without prompts) that survives restarts and is inherited by sub-agents.

Changes

  • Settings: yoloMode: bool in settings.json, serialized as "yoloMode", merged via OR in Settings::merge()
  • effective_config(): forces BypassPermissions when yolo_mode is true
  • CLI: --permission-mode changed to Option<CliPermissionMode>, preserving settings value when unset; --yolo/--dangerously-skip-permissions overrides settings
  • TUI: /yolo slash command toggles at runtime, persists to settings.json, updates config.permission_mode immediately
  • Settings screen: YOLO mode toggle entry
  • Config tool: get/set yoloMode via /config
  • Sub-agents: inherit parent's permission_mode via cloned ToolContext — no extra wiring needed
  • Docs: configuration.md documents yoloMode key

Test plan

  • cargo test --package claurst-core -- yolo_mode — 3 tests pass
  • cargo test --package claurst-tui -- test_yolo_slash_command — passes
  • cargo check --workspace — clean

@alecuba16
alecuba16 force-pushed the feat/yolo-mode branch 4 times, most recently from 7a9128e to 7403259 Compare August 10, 2026 18:16
@alecuba16

Copy link
Copy Markdown
Author

Closing in favor of consolidated group branches. The changes from this PR have been merged into a functional group branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant