β—† Vibe EngineeringSMIT Β· AI Agentic Engineering English
Class 7 Β· 7.3

Rewind in action β€” aur real YOLO mode

Live rewind ke sath checkpoints ko amli shakal dein, phir --dangerously-skip-permissions se milein: woh mode jo kisi cheez ki ijazat nahi maangta aur jis ne ek poori movement shuru ki. Yeh accept-edits se kaise alag hai, aur ise bina kisi afsos ke kaise chalana hai.

🎯 Goal: rewind & YOLO trust ke sath⏱ Read: 10 min🧭 Type: hands-on

Pichhle page ko amli shakal dene ka waqt aa gaya hai. Hum ek real rewind chalayein ge, phir us mode se milein ge jis ne ek poori movement shuru ki: YOLO β€” permissions ko mukammal taur par off karke Claude chalana.

01Rewind, for real

Stage set karein: project ko summarise karein, docs/review.md par likhe gaye code review ka kahein, aur detailed trace ke liye Ctrl+O ke sath ise kaam karte hue dekhein. Demo mein review ne ek pehchani hui galti ki β€” ek "exposed API key" ko flag kiya jo waqai .gitignore mein mehfooz thi. Ise mukkamal taur par sahi karne ke bajaye, hum ne nudge kiya: "Are you sure the API key is exposed?" β€” aur is ne khud problem ko hal kiya aur files fix kein.

Ab hum us hint se pehle rewind kar sakte hain aur farq dekh sakte hain.

/rewind run karein

Steps ki ek list numayan hoti hai, taqriban session resume karne ki tarah. Arrow "current" ko mark karta hai.

Apne matlooba step tak ↑ press karein

"Are you sure…?" ko chhor kar wapas "Please do a code review" par aayein, ya mazeed pichhe "Summarise the project" par.

Choose karein ke kya restore karna hai

Conversation & code dono Β· sirf conversation Β· sirf code Β· ya cancel. Dono pick karein.

1 Summarise 2 Code review ↩ "Are you sure?" β€” rewind yahan karein now
Step 2 par rewind karna conversation ko restore karta hai aur review.md ko hint se pehle ki sthiti par wapas le aata hai β€” "exposed key" wapas aa jati hai.

Iske baad review.md check karein: conversation ke sath sath file bhi revert ho gayi hai. Dono ek sath waqt mein pichhe chale gaye β€” bilkul pichhle page wala checkpoint behavior, jo ab samne agaya hai.

02YOLO kya nahi hai

Jab hum ne "accept edits on" ke liye Shift+Tab press kiya, to ise YOLO kehne ka dil karta tha. Yeh nahi hai. Accept-edits sirf har ek par rukne ke bajaye file diffs ko auto-approve karta hai. Real YOLO kahin ziada aage jata hai.

Accept-edits (Shift+Tab)YOLO (bypass permissions)
File edits approve karta haiHaan, automaticallyHaan
Commands chalane ko approve karta haiNahi β€” ab bhi poochhta haiHaan β€” kisi cheez ke liye nahi poochhta
Is mein kaise enter hote hainA keystroke, mid-sessionA launch flag, deliberately
Risk levelLowReal, agarche frontier model ke sath kam hai

03Real YOLO mode β€” bypass permissions

Pehle commit karein β€” hamesha β€” phir Claude ko aise mode mein launch karein jahan yeh kisi cheez ke liye na poochhe:

terminal Β· living dangerously
git add . && git commit -m "before YOLO"

claude --dangerously-skip-permissions

Yeh flag jaan boojh kar lambi banayi gayi hai β€” Anthropic waqai chahta hai ke aap ko pata ho ke aap risk le rahe hain. Aap ko ek red warning dikhe gi ke Claude potentially dangerous commands chalane se pehle nahi poochhe ga, aur yeh sandboxed container mein use karne ke liye sab se behtar hai. Aage badhein aur zimmedari lein.

Sach bataein, kitna risk hai?

Opus jaise frontier model ke sath destructive kaam hone ka chance bohot kam hai β€” kisi ke drive par rm -rf chalane ka koi mashhoor kissa nahi hai. Lekin yeh ek statistical model hai, is liye probability zero nahi hai. Ise tabhi karein agar aap samajhte hain aur accept karte hain. Sahi sandboxing (next week) hi pros ke liye ise mehfooz banati hai.

Please improve the UI of this project β€” make the horizontal layout look better, use icons instead of delete buttons, and use the horizontal space properly. Make your changes, test everything, and let me know when done.

Yeh ek behtareen contained instruction hai, isi liye UI work ek sensible pehla YOLO hai. Demo mein yeh 7 minutes 44 seconds chala β€” unattended β€” aur ek waqai sharper, mobile-responsive interface ke sath wapas aaya: cards do neat columns mein flow ho gaye, delete actions chhote bin icons ban gaye, aur AI assistant ab bhi kaam kar raha tha. Jo log ise professional taur par karte hain woh kahin ziada grandiose instructions dete hain aur ek ghante ke liye chale jaate hain.

Jab tak commit na ho jaye kabhi bharosa na karein

Jis lamhe YOLO khatam ho aur aap khush hon, snapshot lein: git add . && git commit -m "after UI revamp". Yeh ek single habit hi bekhauf building ko mehfooz banati hai.

βœ“ Aham baatein

  • /rewind prompts ke zariye pichhe jata hai; aap conversation, code, dono, ya kisi ko nahi restore karne ka choose karte hain.
  • Rewind chat aur is ki badli hui files ko ek sath pichhe le jata hai β€” lekin scripts ke zariye touch ki hui files ko nahi.
  • Accept-edits (Shift+Tab) sirf edits ko auto-approve karta hai; YOLO har cheez ko auto-approve karta hai.
  • claude --dangerously-skip-permissions ke sath YOLO mein enter hon β€” hamesha pehle commit karein.
  • Frontier model ke sath risk kam hai lekin non-zero hai; contained tasks (jaise UI) shuru karne ke liye achhi jagah hain.
  • Jaise hi khush hon dobara commit karein. Uncommitted kaam par kabhi bharosa na karein.