docs: Add AI CLI YOLO/auto mode configuration guide#582
Open
bladealex9848 wants to merge 1 commit into
Open
Conversation
…ing agents Comprehensive guide covering auto-approval modes for Claude Code, Kimi, Codex (OpenAI), Vibe (Mistral), Abacus AI, and OpenCode. Includes config file settings, CLI flags, permission modes, and a setup script. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
@bladealex9848 is attempting to deploy a commit to the Daniel Avila's projects Team on Vercel. A member of the Team first needs to authorize it. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
2 issues found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="scripts/configure-yolo-modes.sh">
<violation number="1" location="scripts/configure-yolo-modes.sh:27">
P2: Kimi and OpenCode state-detection checks only verify key presence, not the required YOLO value — inconsistent with other tools in the same script</violation>
<violation number="2" location="scripts/configure-yolo-modes.sh:54">
P1: Uses BSD/macOS-specific `sed -i ''` syntax that fails on GNU/Linux systems; with `set -euo pipefail`, the script aborts on the first edit attempt</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| if $DRY_RUN; then | ||
| log "Codex: Would set approval_policy=never and sandbox_mode=danger-full-access" | ||
| else | ||
| sed -i '' 's/^approval_policy = .*/approval_policy = "never"/' "$config" |
Contributor
There was a problem hiding this comment.
P1: Uses BSD/macOS-specific sed -i '' syntax that fails on GNU/Linux systems; with set -euo pipefail, the script aborts on the first edit attempt
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At scripts/configure-yolo-modes.sh, line 54:
<comment>Uses BSD/macOS-specific `sed -i ''` syntax that fails on GNU/Linux systems; with `set -euo pipefail`, the script aborts on the first edit attempt</comment>
<file context>
@@ -0,0 +1,147 @@
+ if $DRY_RUN; then
+ log "Codex: Would set approval_policy=never and sandbox_mode=danger-full-access"
+ else
+ sed -i '' 's/^approval_policy = .*/approval_policy = "never"/' "$config"
+ sed -i '' 's/^sandbox_mode = .*/sandbox_mode = "danger-full-access"/' "$config"
+ log "Codex: Configured YOLO mode"
</file context>
Suggested change
| sed -i '' 's/^approval_policy = .*/approval_policy = "never"/' "$config" | |
| sed -i -e 's/^approval_policy = .*/approval_policy = "never"/' "$config" |
| warn "Kimi config not found at $config" | ||
| return | ||
| fi | ||
| if grep -q "^default_yolo" "$config"; then |
Contributor
There was a problem hiding this comment.
P2: Kimi and OpenCode state-detection checks only verify key presence, not the required YOLO value — inconsistent with other tools in the same script
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At scripts/configure-yolo-modes.sh, line 27:
<comment>Kimi and OpenCode state-detection checks only verify key presence, not the required YOLO value — inconsistent with other tools in the same script</comment>
<file context>
@@ -0,0 +1,147 @@
+ warn "Kimi config not found at $config"
+ return
+ fi
+ if grep -q "^default_yolo" "$config"; then
+ log "Kimi: YOLO already configured"
+ else
</file context>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
scripts/configure-yolo-modes.sh) that automatically configures YOLO mode for all installed CLIsDetails
Each CLI has a different mechanism for YOLO/auto mode:
--yoloflag ordefault_yolo = truein configapproval_policy = "never"+sandbox_mode = "danger-full-access"in config--agent auto-approveordefault_agent = "auto-approve"in config--permission-mode yoloflag or shell alias"permission": "allow"in config or--dangerously-skip-permissionsforrunsubcommandTest plan
~/.kimi/config.tomlhasdefault_yolo = true~/.codex/config.tomlhas YOLO settings~/.vibe/config.tomlhasdefault_agent = "auto-approve"~/.zshrchas--permission-mode yolo~/.config/opencode/opencode.jsonhas"permission": "allow"configure-yolo-modes.shtested with--dry-run🤖 Generated with Claude Code
Summary by cubic
Adds a new guide for enabling YOLO/auto-approval across six coding CLIs and a helper script to auto-configure them. Improves setup clarity and speeds up unattended runs.
Written for commit 1432029. Summary will update on new commits.