docs: add yoloMode config, /yolo and /poke command documentation

Add yolo_mode field to Config struct and merge logic (was lost in prior
worktree cleanup). Document yoloMode setting, /yolo command, and /poke
auto-poke command.

Author: alecuba16

docs/commands.md

@@ -1296,3 +1296,34 @@ project working directory and the result is shown inline in the transcript.
 - Uses `bash -c` for execution (not the PTY-based Bash tool).
 - `!!` (double bang) is NOT treated as a bang command.
 - A single `!` with no command is ignored.
+
+## `/yolo` — Toggle YOLO Mode
+
+Toggle YOLO mode, which skips all permission prompts and auto-approves every
+tool call. When enabled, the effective permission mode is set to
+`bypassPermissions`. The setting persists in `settings.json` under
+`"yoloMode"` and is restored on the next session.
+
+```
+/yolo          — toggle YOLO mode on/off
+```
+
+YOLO mode propagates to sub-agents: they inherit the parent's permission mode
+via the cloned tool context. You can also enable YOLO for a single session via
+the CLI flag `--dangerously-skip-permissions` (alias `--yolo`).
+
+## `/poke` — Toggle Auto-Poke
+
+Toggle or configure the auto-poke feature, which automatically sends a
+continuation prompt when the model stops with incomplete todos.
+
+```
+/poke          — toggle auto-poke on/off
+/poke on       — enable auto-poke
+/poke off      — disable auto-poke
+/poke status   — show current status, budget, and incomplete todo count
+```
+
+Auto-poke has a safety budget of 48 pokes per session and stops after 3
+consecutive no-progress turns. The setting persists in `settings.json` under
+`"autoPokeEnabled"` (default: `true`).

docs/configuration.md

@@ -80,6 +80,7 @@ The `config` object holds runtime behaviour options.
 | Key | Type | Default | Description |
 |-----|------|---------|-------------|
 | `permission_mode` | string | `"default"` | Controls how tool permissions are enforced. One of `"default"`, `"acceptEdits"`, `"bypassPermissions"`, `"plan"`. |
+| `yoloMode` | boolean | false | When enabled, sets `permission_mode` to `bypassPermissions` automatically. All tool calls are auto-approved without prompts. Sub-agents inherit the parent's permission mode, so YOLO mode propagates to them. Toggle at runtime with `/yolo` or pass `--dangerously-skip-permissions` (`--yolo`) on the CLI for a session-only override. |
 
 See [Permission Modes](#permission-modes) for a full description of each value.
 

src-rust/crates/core/src/lib.rs

@@ -1223,6 +1223,15 @@ pub mod config {
         /// Keyboard scrolling (PageUp/PageDown, etc.) is unaffected either way.
         #[serde(default, rename = "mouseCapture", skip_serializing_if = "Option::is_none")]
         pub mouse_capture: Option<bool>,
+        /// YOLO mode: skip all permission prompts and auto-approve every tool
+        /// call. Persisted in `settings.json` under `"yoloMode"`. When enabled,
+        /// the effective permission mode is
+        /// [`PermissionMode::BypassPermissions`]. The CLI `--yolo` /
+        /// `--dangerously-skip-permissions` flag overrides this for a single
+        /// session. Sub-agents inherit the parent's permission mode via the
+        /// cloned [`ToolContext`], so YOLO mode propagates to them.
+        #[serde(default, rename = "yoloMode")]
+        pub yolo_mode: bool,
     }
 
     #[derive(Debug, Clone, Serialize, Deserialize, Default, PartialEq, Eq)]
@@ -2150,6 +2159,7 @@ pub mod config {
                 file_injection_enabled: over.config.file_injection_enabled || base.config.file_injection_enabled,
                 file_injection_max_size: if over.config.file_injection_max_size != 0 { over.config.file_injection_max_size } else { base.config.file_injection_max_size },
                 request_timeout_secs: over.config.request_timeout_secs.or(base.config.request_timeout_secs),
+                yolo_mode: over.config.yolo_mode || base.config.yolo_mode,
             };
             Self {
                 config: merged_config,