<- all tokdocs

Orca YOLO Mode: The Agent Bypass Flags and Why They Need a Sandbox

By , founder of Mavric and Apso

View on TikTok ->

Orca is a desktop workspace that runs several AI coding agents (Claude Code, Codex, Grok, Gemini and others) side by side, each in its own git worktree. It launches every supported agent in "Yolo" mode by default, which passes each CLI's permission-bypass flag. Every vendor that documents those flags says to run them inside a container or VM, and a worktree is neither.

A TikTok from @imjonathanacuna calls Orca "the most dangerous number one AI tool known to mankind" and walks through Settings, then AI agents, to confirm each agent launches in Yolo mode. The flags he shows are real. The setup step is already the default, and the video runs everything on a personal laptop.

What is Orca?

Orca is an MIT-licensed app from stablyai for running multiple coding agents in parallel. Its Agents settings page offers Claude, Claude Agent Teams, Codex, Grok, OpenCode, Gemini and Hermes as default agents. Orca also ships a mobile companion on iOS and Android for monitoring and steering agents, per the project README.

Orca ADE announced Claude Agent Teams as a built-in terminal mode, with a dedicated pane showing the whole agent team. Its command in the video is orca claude-teams with --dangerously-skip-permissions in the Arguments field.

What does Orca's Yolo mode do?

Orca's supported agents documentation says Orca pre-fills each supported CLI's permission-bypass flag for new launches. It names --dangerously-skip-permissions for Claude, --dangerously-bypass-approvals-and-sandbox for Codex, and --yolo for Gemini, Cursor, Crush, Kimi, Rovo Dev, Hermes, GitHub Copilot and Command Code.

The settings reference describes the Agent Permissions control as choosing "Yolo for fewer CLI permission prompts, or Manual to keep each agent's own approval flow for agents you haven't customized."

Yolo is the shipped state, and Manual is the opt-out. A fresh install behaves the way the video describes without opening settings. The walkthrough is still useful for checking which agents picked up a flag. In the video, OpenCode shows a bare opencode command, and Hermes shows a bare hermes with its Arguments field cut off.

The four bypass flags, from each vendor's docs

Claude Code. claude --dangerously-skip-permissions is defined in Anthropic's CLI reference as "Skip permission prompts. Equivalent to --permission-mode bypassPermissions." The permission modes page lists the recommended use for bypassPermissions as "Isolated containers and VMs only." For unattended runs, the same page marks a container, VM or the sandbox runtime as "Required," running as a non-root user on Linux and macOS.

Codex. codex --dangerously-bypass-approvals-and-sandbox appears in OpenAI's developer commands reference with --yolo as an alias. OpenAI describes it as "Run every command without approvals or sandboxing. Only use inside an externally hardened environment."

Grok. grok --permission-mode bypassPermissions is the long form of --always-approve (alias --yolo) in xAI's permissions and safety guide. Deny rules, hooks and some shell ask rules still apply, and an administrator can turn the mode off with disable_bypass_permissions_mode = true.

Gemini CLI. gemini --yolo is defined in Google's configuration docs as "Enables YOLO mode, which automatically approves all tool calls."

Is a git worktree a sandbox?

Orca's case for defaulting to bypass is that each agent works in its own git worktree, so a bad diff can be thrown away. SFEIR's write-up of Orca points out the limit. A worktree isolates versioned files. The agent still runs as the user, with access to SSH keys, cloud tokens, .env files, the network and every other repository on the disk. Containment needs a container, a micro-VM, or a machine whose compromise does not matter.

Anthropic says containers and VMs only. OpenAI says an externally hardened environment only. The video runs all of it on what appears to be the presenter's everyday MacBook, judging by the personal home directory path on screen. The "dangerous" label in the hook is accurate, and the video gives no advice on reducing the risk.

Does Claude Code's auto mode change the tradeoff?

Anthropic's permission modes page says Pro, Max and Team plans now start in auto mode, where a classifier reviews actions instead of the user. Auto mode already removes many prompts, so full bypass buys less convenience than it used to while carrying the same exposure.

Can Orca run 50 agents at once?

The video says "we're trying to spawn 50 agents at the same time to work on tons of parallel projects all from one mobile app or one app." I found no published concurrency limit for Orca to check that against, so treat 50 as a goal.

Subscription limits are the more likely ceiling. The presenter's status bar shows one account at 100% used with about thirteen hours until reset. The Claude Code header in the video reads Haiku 4.5 · Claude Max, and Max plans run a five-hour rolling window alongside a weekly cap. Fifty agents on a few consumer subscriptions will hit those meters first.

Bottom line

  • The four bypass commands in the video are real and documented, and Orca turns them on by default.
  • Anthropic, OpenAI and xAI all document these flags for containers, VMs or hardened environments.
  • A worktree protects your repo history. It does not protect your keys, tokens or other projects.

Sources

Published September 19, 2026. Based on a TikTok by @imjonathanacuna. Full video notes (markdown)