Class 13 · 13.1

Sandboxing, aur yeh mazaydar hissa kyun hai

Aaj hum YOLO ko safe banayenge. “Sandboxing” sookhi security homework jaisi lagti hai, lekin poore course ki sab se exciting super-power kholti hai: Claude ko azaadi se chalne dena jab ke us ka koi kaam aap ko nuqsan nahi pohancha sakta. Aayiye wajah samjhein aur teen tareeqe map karein.

🎯 Goal: understand sandboxing & the 3 approaches⏱ Read: 15 min🧠 Type: concept

Kal poora pro toolkit ek dawat tha. Agar aap thore overwhelmed mehsoos kar rahe the to yeh bilkul normal hai, aur yahi reaction Andrej Karpathy ne options ki chakkar dene wali tadaad par apne mashhoor tweet mein capture kiya tha. Naye material se pehle saans lein: aap ko har din yeh sab zaroorat nahi.

01Hum kahan hain (chhota sa khulasa)

Jo pro toolkit aap seekh chuke hain, us ka saaf aur be-fikr version yeh hai:

rozana use

Skills

Yeh universal standard ban chuki hain — Anthropic ne invent kiya, lekin ab Codex, OpenCode aur doosre bhi use karte hain. Slash-commands ki jagah zyada tar skills ne le li hai.

aksar use

Sub-agents

Task isolated context ko dein aur sirf result wapas lein. Isay use karne ki asal wajah context window ko bachana hai.

kabhi kabhi

Hooks

Sirf khaas problem hal karne ke liye use karein. Ab aap jaante hain ke yeh maujood hain aur docs kahan hain.

kam

Plugins aur marketplaces

Skills/agents ko team ke saath share karne ke liye package karne mein kaam aate hain. Rozana ki cheez nahi.

Andrej ke tweet ki woh pur-asrar file

Plugin folder mein .mcp.json (saath aane wale MCP servers) aur .lsp.json bhi ho sakta hai — Language Server Protocol config. LSP Claude Code ko programming language ke rules sikhata hai taake yeh likhe hue code ko validate kar sake. Claude aam languages jaanta hai; exotic language support ke liye hi .lsp.json add karenge. Mumkin hai kabhi zaroorat na pade, lekin ab tweet dobara parhenge to har line samajh aayegi.

Isay pakka karne ka behtareen tareeqa

Exercises ek baar waqai karein: slash-command, sub-agent aur hook banayein, aur chhota plugin package karein. Ek baar amal karne se “main ne is ke bare mein parha hai” badal kar “main yeh kar sakta hoon” ban jata hai.

02“Sandboxing” ka asal matlab

Sandbox us cheez ke gird ring-fence hai jise agent chhoo sakta hai. Goya aap kehte hain: “is box ke andar azaadi se chalo — parho, likho, scripts chalao — lekin is se bahar nahi pohanch sakte.” Do fences sab se aham hain:

Do fences: file system (isi folder ke andar rahna) aur network (sirf yeh sites). Box ke andar sab kuch jaiz hai.

Faida sirf security nahi — productivity bhi hai. Box safe hone ki wajah se aap asli risk ke baghair “YOLO” level ki azaadi se khush ho kar kaam kar sakte hain. Aap Claude ko bas jaane dene par tayyar ho jate hain.

Pichlay haftay yaad hai jab kaha tha, “waqai YOLO karne se pehle shayad sandboxing ka intezar karein”? Woh lamha ab aa gaya. Ab kar sakte hain.

03Chhupa hua faida: approval fatigue ko harana

Un-sandboxed duniya mein Claude risky actions ki permission maangta hai aur aap approve karne ke liye 2 (ya step-by-step ke liye 1) dabate hain. Safe lagta hai, lekin ek trap hai.

1-1-1-1 ka masla

Daswein prompt ke baad dimagh parhna band kar deta hai. Aap autopilot par bas 1…1…1…1 dabate rehte hain. Yeh approval fatigue hai, aur iska matlab hai ke “safe” un-sandboxed workflow mehsoos hone se kam safe ho sakta hai — aap un cheezon ko stamp kar rahe hote hain jinhein waqai check nahi kiya.

Sandbox isay ulat deta hai. Box ke andar actions auto-approved hote hain kyun ke pehle se safe hain — rubber-stamp karne ko kuch nahi. Aap ko YOLO ki speed aur asli safety net milti hai, fake nahi. Yeh teesra aur behtareen flavour hai: ek saath secure aur productive.

04Sandbox karne ke teen tareeqe

Aaj baqi waqt teen techniques ke liye hai. Instructor ne inhein rangon se code kiya hai — yeh map zehan mein rakhein warna asani se gum ho sakte hain:

Blue · local

Native sandbox

Claude Code mein built-in. /sandbox type karein. Halka OS-level box jo aap ki machine par chalta hai. (13.2)

Purple · managed cloud

Claude Code on the Web

Anthropic aap ke liye cloud sandbox mein Claude chalata hai — browser, mobile, terminal ya GitHub issue. (13.3)

Yellow · 3rd-party

Third-party sandbox

Doosri company (misal ke taur par fly.io ka Sprites.dev) coding agents ke liye bana cloud box deti hai. (13.4)

Har ek ek jumlay mein

Blue = laptop par aap ka apna halka Docker. Purple = Anthropic machines par “Claude, yeh kahin aur chalao”. Yellow = specialist se tez, isolated Linux box rent karke us mein koi bhi agent chalana.

05Docker aur dev-containers par ek baat

Agar aap Docker (ya VS Code ke .devcontainers) se waqif hain to aap “box ke andar box” paane ka asal tareeqa jaante hain. Yeh ab bhi kaam karta hai aur aap hamesha use kar sakte hain. Lekin aaj ki har cheez is se ek qadam aage hai — native sandbox Docker se halka hai aur cloud options remote execution bhi dete hain. Docker ko us bunyaad ki tarah samjhein jise hum behtar kar rahe hain, na ke pehle se set up karna zaroori hai.

✓ Ahm baatein

Sandbox file system aur network ko ring-fence karta hai taake agent asal risk ke baghair azaadi se chale.
Asal inaam safe productivity hai — yeh approval fatigue (1-1-1-1 autopilot) ka ilaaj karta hai.
Teen approaches: Blue native/local, Purple managed cloud, Yellow third-party cloud.
Docker/dev-containers ab bhi kaam karte hain — aaj hum un se aage ja rahe hain.