YOLO mode

    What is YOLO mode?

    SHORT ANSWER

    YOLO mode is a setting in AI coding tools that lets the AI run commands, install packages and edit files without asking you to approve each step. It's fast, and it means any mistake, or any malicious instruction the AI picks up, runs with your full permissions.

    Also called: Auto-approve, skip permissions

    ON THIS PAGE

    What it means

    Normally, an AI coding tool pauses and asks before it does something risky. YOLO mode switches those prompts off. In Claude Code the flag is called --dangerously-skip-permissions, and other tools have similar auto-run options.

    The danger isn't that the AI is out to get you. It might misread a task, or follow instructions hidden in a web page, file or package it reads. Without a pause, nobody is there to say no.

    Why it matters for vibe-coded apps

    Constantly clicking "approve" is annoying, so it's tempting to switch it off. But the tool then runs with whatever your computer, accounts and keys can do.

    IF THIS IS WRONG IN YOUR APP
    • A wrong command can delete files or overwrite your data.
    • Hidden instructions in code or web pages (prompt injection) can run unseen.
    • Keys and tokens on your machine are within reach of whatever it runs.

    Example

    Running an AI agent on your everyday laptop.

    ✕ RISKYFull permissions, no questions, real keys nearby
    claude --dangerously-skip-permissions
    # runs on your main machine, with production keys in ~/.env
    ✓ SAFERIsolated, with only what the job needs
    # Throwaway container or VM, test keys only, a fresh git branch
    docker run --rm -it -v "$PWD":/work -w /work agent-sandbox
    # ...then review the diff before merging

    If you do use auto-approve, do it only in a sandbox with no production secrets, and read every change before you merge.

    How to check if your app has this problem

    1. 1Look in your AI tool's settings for options like auto-run, auto-approve or skip permissions.
    2. 2Check which keys and tokens are reachable from the folder the tool works in.

    The quicker way: LetMeCheck tests for this automatically, from the outside, the way an attacker would.

    Run a free scan →

    How to fix it

    1. 1Keep approvals on for anything that deletes, installs or deploys.
    2. 2If you need auto-run, use a container or separate machine with test keys only.
    3. 3Work on a git branch and review the full diff before merging.
    4. 4Never leave production keys where the agent can read them.
    FIX PROMPT · PASTE INTO YOUR AI TOOL

    Help me set up a safe environment for running an AI coding agent with auto-approve: a Docker container with only the project folder mounted, test credentials only, no network access to production, and a git branch I can review before merging.

    Check if your app has this problem

    Paste your website and we'll check for YOLO mode issues and other common issues in AI-built apps. Free, about a minute, and nothing on your site is changed.

    Last updated