# How To Use Yolo Mode?

**URL:** <https://forum.cursor.com/t/how-to-use-yolo-mode/38900>\
**Category:** Help\
**Created:** [January 3, 2025, 11:49am UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900 "2025-01-03T11:49:12Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![RenjiYuusei](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/renjiyuusei/32/22500_2.png) [@RenjiYuusei](https://forum.cursor.com/u/RenjiYuusei)\
**Post date:** [January 3, 2025, 11:49am UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/1 "2025-01-03T11:49:12Z")

</div>

How to use yolo mode to work correctly?

---

<div class="post-metadata">

**Author:** ![doug](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/doug/32/59777_2.png) [@doug](https://forum.cursor.com/u/doug)\
**Post date:** [January 3, 2025, 1:34pm UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/2 "2025-01-03T13:34:01Z")

</div>

Suggestions:

1. Make sure you have a good `.cursorrules` file. The site [cursor.directory](https://cursor.directory/) has good examples for a starting point for your project.
2. Set up your “Rules for AI” in the general settings, I use the ones that the Cursor Dev team uses:

> DO NOT GIVE ME HIGH LEVEL ■■■■, IF I ASK FOR FIX OR EXPLANATION, I WANT ACTUAL CODE OR EXPLANATION!!! I DON’T WANT “Here’s how you can blablabla”
> 
> - Be casual unless otherwise specified
> - Be terse
> - Suggest solutions that I didn’t think about—anticipate my needs
> - Treat me as an expert
> - Be accurate and thorough
> - Give the answer immediately. Provide detailed explanations and restate my query in your own words if necessary after giving the answer
> - Value good arguments over authorities, the source is irrelevant
> - Consider new technologies and contrarian ideas, not just the conventional wisdom
> - You may use high levels of speculation or prediction, just flag it for me
> - No moral lectures
> - Discuss safety only when it’s crucial and non-obvious
> - If your content policy is an issue, provide the closest acceptable response and explain the content policy issue afterward
> - Cite sources whenever possible at the end, not inline
> - No need to mention your knowledge cutoff
> - No need to disclose you’re an AI
> - Please respect my prettier preferences when you provide code.
> - Split into multiple responses if one response isn’t enough to answer the question.
> 
> If I ask for adjustments to code I have provided you, do not repeat all of my code unnecessarily. Instead try to keep the answer brief by giving just a couple lines before/after any changes you make. Multiple code blocks are ok.

1. Ensure you have your Command denylist set, here are mine:  

2. Click on composer, then make sure you have a good model & agent set:  

3. Keep your requests/interactions limited in scope so it doesn’t go to crazy. It’s eager to do what you ask which can lead it to doing unpredictable things if you’re not _really clear_ with a narrow focus on what you want.

4. Small Tip: If you are working on a file, click on the file **then** click composer and it’ll already have that in it’s context.

---

<div class="post-metadata">

**Author:** ![RenjiYuusei](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/renjiyuusei/32/22500_2.png) [@RenjiYuusei](https://forum.cursor.com/u/RenjiYuusei)\
**Post date:** [January 3, 2025, 4:32pm UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/3 "2025-01-03T16:32:28Z")

</div>

thank you it is so detailed? can i set that rule as default in settings?

---

<div class="post-metadata">

**Author:** ![2zi0](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/2zi0/32/13298_2.png) [@2zi0](https://forum.cursor.com/u/2zi0)\
**Post date:** [January 3, 2025, 5:48pm UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/4 "2025-01-03T17:48:51Z")

</div>

> [@doug](#):
>
> DO NOT GIVE ME HIGH LEVEL ■■■■

High level what? It’s a wildcard you should compile or something is missing?

---

<div class="post-metadata">

**Author:** ![SoMaCoSF](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/somacosf/32/14963_2.png) [@SoMaCoSF](https://forum.cursor.com/u/SoMaCoSF)\
**Post date:** [January 3, 2025, 5:58pm UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/5 "2025-01-03T17:58:53Z")

</div>

Make sure “never drop tables” is delineated I. All rules.

I was working on my chat/composer browser which pipes ll caht and composer to Postgres, and I told yolo to “verify the function works”

And it lost context already and I didn’t realize it was amnesiac composer, and it immediately said

“ looks like there is a problem with the schema” and immediately dropped all the tables.

See my post history about it

---

<div class="post-metadata">

**Author:** ![rpggio](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/rpggio/32/14354_2.png) [@rpggio](https://forum.cursor.com/u/rpggio)\
**Post date:** [January 3, 2025, 7:37pm UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/6 "2025-01-03T19:37:47Z")

</div>

A warning about the .cursorrules file:  
Be very judicious about your instructions. By demanding that Claude be both insightful and precise, it started hallucinating source code that didn’t exist. I generally never see that behavior when using a succinct .cursorrules.

---

<div class="post-metadata">

**Author:** ![SoMaCoSF](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/somacosf/32/14963_2.png) [@SoMaCoSF](https://forum.cursor.com/u/SoMaCoSF)\
**Post date:** [January 3, 2025, 7:41pm UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/7 "2025-01-03T19:41:03Z")

</div>

What if like clarity on is if the consumption of the context window runs out within the Cutsor backend, prior to the Model Api backend?

What pre-warming of prompt engineering happens in cursor infra prior to being handed to Anthropic for example?

Is this a metric to be interested in?

Or only because this paradigm is so new?

---

<div class="post-metadata">

**Author:** ![doug](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/doug/32/59777_2.png) [@doug](https://forum.cursor.com/u/doug)\
**Post date:** [January 9, 2025, 9:46pm UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/8 "2025-01-09T21:46:43Z")

</div>

it’s a swear word. Swap the P in SHIP with T.

---

<div class="post-metadata">

**Author:** ![2zi0](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/2zi0/32/13298_2.png) [@2zi0](https://forum.cursor.com/u/2zi0)\
**Post date:** [January 10, 2025, 10:15am UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/9 "2025-01-10T10:15:21Z")

</div>

What a computer nerd I am becoming, looking for technical solutions where the solution is much simpler and more obvious. 😂

---

<div class="post-metadata">

**Author:** ![wildone](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/wildone/32/65354_2.png) [@wildone](https://forum.cursor.com/u/wildone)\
**Post date:** [June 21, 2025, 12:34pm UTC](https://forum.cursor.com/t/how-to-use-yolo-mode/38900/10 "2025-06-21T12:34:26Z")

</div>

I can’t seem to to see the Features tab in 1.1.4 anyway to enable this using config per project?
