WeWorkBuddy

[分享创造] 分享一个自用的小工具: yolo-ai,用一个前缀统一所有 AI CLI 的权限跳过开关

用 Claude Code 、Codex 、Gemini CLI 这些工具的朋友应该都有同感:权限提示太频繁了。 每个 AI CLI 跳过权限的参数都不一样:Claude 是 --dangerously-skip-permissions ,Codex 是 --dangerously-bypass-approvals-and-sandbox ,Gemini 和 Qwen 又换成了 --yolo ,Aider 则是 --yes-always 。装了三四个工具之后,根本记不住。 我写了一个很小的 npm 包来解决这个问题: yolo-ai 。 GitHub: https://github.com/2501224066/yolo-ai 核心逻辑就一句话:用 yolo 前缀调用任何一个 AI CLI ,它会自动把该工具对应的“跳过权限”参数塞进去,然后把终端交还给子进程。 用法 npm install -g yolo-ai 然后: yolo claude # → claude --dangerously-skip-permissions yolo codex # → codex --danger

Read original source
Source reference for [分享创造] 分享一个自用的小工具: yolo-ai,用一个前缀统一所有 AI CLI 的权限跳过开关. Screenshot not yet available.
Source record · preview pending · www.v2ex.comOpen the source for the full page.

Source record

Research analysis

Project record

Source account: 用 Claude Code 、Codex 、Gemini CLI 这些工具的朋友应该都有同感:权限提示太频繁了。 每个 AI CLI 跳过权限的参数都不一样:Claude 是 --dangerously-skip-permissions ,Codex 是 --dangerously-bypass-approvals-and-sandbox ,Gemini 和 Qwen 又换成了 --yolo ,Aider 则是 --yes-always 。装了三四个工具之后,根本记不住。 我写了一个很小的 npm 包来解决这个问题: yolo-ai 。 GitHub: https://github.com/2501224066/yolo-ai 核心逻辑就一句话:用 yolo 前缀调用任何一个 AI CLI ,它会自动把该工具对应的“跳过权限”参数塞进去,然后把终端交还给子进程。 用法 npm install -g yolo-ai 然后: yolo claude # → claude --dangerously-skip-permissions yolo codex # → codex --danger

Observed adoption & comparisons

Recent records to compare: “D4Vinci/Scrapling” (GitHub Trending, Nov 5, 2026); “garrytan/gstack” (GitHub Trending, Nov 5, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.

Adoption decision

Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.

Unverified requirements

Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.

Next test

Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.