mirror of
https://github.com/cline/cline.git
synced 2026-09-21 05:10:09 +08:00
Juan Pablo Flores
246b0fa999
* docs: update what-is-cline to use generic IDE references Updated documentation to replace VS Code-specific references with generic "IDE" terms, making it applicable to modern IDEs beyond VS Code for broader compatibility. * docs: expand Cline installation guide with comprehensive setup instructions - Add prerequisites section with account creation and editor compatibility - Include detailed installation steps for VS Code/Cursor and JetBrains IDEs - Add troubleshooting sections for common installation issues - Expand editor support information and setup guidance - Improve documentation structure with tabs and accordions for better UX * docs: remove font weight and reorder getting started pages - Remove font weight property from fonts configuration - Reorder getting started pages to place installation before model selection guide * fixes title font-weight to original values * docs: improve JetBrains plugin installation link text Replace generic URL text with descriptive "JetBrains Marketplace" link text for better user experience and accessibility in the Cline installation guide. * docs: add voice mode feature documentation and cross-references Add comprehensive documentation for Voice Mode feature including setup instructions, use cases, and technical requirements. Also add cross-reference tip in plan-and-act.mdx to promote voice mode usage during planning discussions. * docs: rename voice-mode to dictation for clarity Rename voice-mode.mdx to dictation.mdx and update all references throughout the documentation to use "Dictation" instead of "Voice Mode" for more accurate terminology and better user understanding. * feat(docs): add YOLO mode documentation Add comprehensive documentation for YOLO mode feature, covering auto-approval functionality, safety warnings, use cases, and best practices for autonomous operation. * docs: reorganize navigation structure and add redirect for JetBrains install page - Remove JetBrains installation page from getting-started section - Reorder Features section with @ Mentions first, followed by alphabetically sorted individual features - Move Slash Commands group after individual features and add workflows page - Add yolo-mode feature to the end - Add redirect from old JetBrains install path to main installation guide * docs: improve JetBrains logo visibility and simplify dictation instructions - Remove Frame wrapper around JetBrains logo for cleaner markup - Add CSS styling to ensure JetBrains logo visibility in dark mode with background, border, and hover effects - Simplify dictation instructions by removing redundant recording state description
84 lines
4.2 KiB
Plaintext
84 lines
4.2 KiB
Plaintext
---
|
|
title: "YOLO Mode"
|
|
sidebarTitle: "YOLO Mode"
|
|
---
|
|
|
|
YOLO mode is exactly what it sounds like - Cline auto-approves everything. Check the box in feature settings and he'll execute file changes, terminal commands, even transitions from Plan to Act mode without asking.
|
|
|
|
Think of it as [Auto Approve](/features/auto-approve) on steroids - instead of granular permissions, YOLO mode gives Cline complete autonomy.
|
|
|
|
<Note>
|
|
**Warning: This is dangerous.** YOLO mode disables all safety checks. Cline will execute whatever he decides without asking permission.
|
|
</Note>
|
|
|
|
## What Gets Auto-Approved
|
|
|
|
When YOLO mode is enabled, Cline automatically approves:
|
|
|
|
- **All file operations** - reading, writing, and modifying files anywhere on your system
|
|
- **All terminal commands** - including potentially destructive operations
|
|
- **Browser actions** - web scraping, form submissions, navigation
|
|
- **MCP server tools** - external integrations and API calls
|
|
- **Mode transitions** - automatic switching from Plan to Act mode
|
|
|
|
Essentially, every safety guardrail is removed. Cline operates with complete autonomy.
|
|
|
|
## How to Enable YOLO Mode
|
|
|
|
Navigate to Cline Settings → Features and check the "YOLO Mode" box. That's it - no confirmation dialogs, no additional warnings. Once enabled, Cline will start auto-approving all actions immediately.
|
|
|
|
To disable it, simply uncheck the box. Any pending actions will still require your approval once YOLO mode is turned off.
|
|
|
|
## When You Might Use This
|
|
|
|
YOLO mode was built primarily for our upcoming scriptable CLI where fully autonomous execution makes sense. In the GUI, you might consider it for:
|
|
|
|
**Rapid prototyping** where you want zero friction and don't care about potential mistakes. Perfect for throwaway experiments or exploring new ideas quickly.
|
|
|
|
**Trusted, repetitive tasks** where you've already validated Cline's approach and want to eliminate approval overhead. Think routine refactoring or well-established patterns.
|
|
|
|
**Demonstration purposes** where you want to show Cline's capabilities without constant interruptions.
|
|
|
|
## What Could Go Wrong
|
|
|
|
Since YOLO mode removes all safety checks, Cline could:
|
|
|
|
- Delete important files without warning
|
|
- Execute commands that modify system settings
|
|
- Make network requests to external services
|
|
- Overwrite configuration files
|
|
- Install or uninstall software packages
|
|
- Commit and push changes to version control
|
|
|
|
The risk level depends entirely on what you ask Cline to do. Simple tasks remain relatively safe, but complex requests can have unpredictable consequences.
|
|
|
|
## Best Practices
|
|
|
|
If you decide to use YOLO mode:
|
|
|
|
**Start with isolated environments.** Use it in throwaway projects or sandboxed environments first. Never enable it on production codebases until you understand the risks.
|
|
|
|
**Be specific with requests.** Vague instructions combined with unlimited permissions can lead to unexpected results. The clearer your requirements, the more predictable Cline's actions.
|
|
|
|
**Monitor the output.** Even though Cline doesn't ask for permission, he still shows you what he's doing. Watch the terminal output and file changes as they happen.
|
|
|
|
**Keep version control handy.** Make sure you can easily revert changes if something goes wrong. Git becomes your safety net when YOLO mode is your workflow.
|
|
|
|
## Inspiration: What Becomes Possible
|
|
|
|
With YOLO mode enabled, you can:
|
|
|
|
**Build entire applications** from a single prompt. Describe what you want and let Cline handle everything - file creation, dependency installation, configuration setup, even deployment scripts.
|
|
|
|
**Automate complex workflows** that normally require dozens of approval clicks. Data processing pipelines, build system setup, or multi-step refactoring operations become seamless.
|
|
|
|
**Rapid iteration cycles** where you can quickly test ideas without approval friction. Perfect for exploring different approaches or experimenting with new technologies.
|
|
|
|
**Live demonstrations** where you can show Cline's full capabilities without stopping to approve every action. Great for presentations or teaching scenarios.
|
|
|
|
The key is understanding that YOLO mode transforms Cline from an interactive assistant into an autonomous agent. Use that power wisely.
|
|
|
|
---
|
|
|
|
Questions or feedback? Reach us in our [Discord](https://discord.gg/cline) or [r/cline](https://reddit.com/r/cline).
|