Class 13 · 13.5

Sandboxing ka khulasa aur cheat-sheet

Sab kuch ek page par. Yeh poori Class 13 hai — teenon approaches saath saath, kis waqt kaunsi use karni hai, tamam commands ek jagah aur chhota self-check taake pata chale baat yaad reh gayi.

🎯 Maqsad: jama karna aur reference ke liye rakhna⏱ Parhein: 10 min📝 Qisam: reference

Aaj hum ne YOLO ko teen mukhtalif tareeqon se safe banaya. Agar sab kuch mix ho gaya ho to yeh page aap ka anchor hai — bookmark kar lein.

01Teen approaches, ek tasveer

Blue laptop par chalta hai; purple aur yellow cloud mein. Teenon Claude ko azaadi se kaam karne dete hain baghair na-munasib cheez ko chhuye.

02Mujhe kaunsa use karna chahiye?

Agar aap chahte hain…	Use	Kyun
Apne laptop par safe kaam auto-approve ho	Blue · /sandbox	Sab se halka, foran, accounts ke baghair. (Windows: WSL chahiye.)
Tasks chala kar laptop khaali rakhein	Purple · web	Anthropic machines par chalta hai; aap PR review karte hain.
Phone se ya chalte phirte kaam karein	Purple · mobile	Wohi cloud sessions, Claude app se.
Backlog parallel clear karein	Purple · @claude	Kai GitHub issues tag karein; cloud Claudes ka fleet.
Kisi bhi agent ke liye tez persistent remote dev box	Yellow · Sprites	Isolated, stateful, agent-agnostic, full-YOLO safe.

03Command cheat-sheet

every command from today

# --- BLUE: native sandbox ---
/sandbox                     # configure & enable (pick mode 1 = sandboxed YOLO)

# --- PURPLE: managed cloud (one-time setup) ---
/install-github-app          # installs gh CLI + the two workflows
gh auth login                 # log this machine into GitHub
# then, five ways to run remote:
> & <your task>               # 1. ampersand prefix, inside Claude
claude --remote "<task>"       # 2. from the terminal
# 3. browser  claude.ai/code   4. Claude mobile app  Code tab
# 5. GitHub issue, tag  @claude
/tasks                       # see everything running remotely

# --- YELLOW: Sprites.dev ---
<paste install one-liner>     # installs sprite CLI (contains your key)
sprite login
sprite create my-worker       # <1s; prompt becomes sprite@sprite
git clone <repo> && cd <repo>
claude                        # pre-installed; /resume to continue a session

04Security checklist

Full-YOLO par jane se pehle

Sandbox config mein wazeh deny rules rakhein — yeh hamesha laagu hoti hain.
Native sandbox mein network ke liye sirf woh sites allow-list karein jin ki waqai zaroorat ho.
Aisi command kabhi paste ya share na karein jis mein key ho (Sprite install line mein hai).
Full-YOLO is liye safe hai ke box isolated hai — sirf real sandbox ke andar chalayein, bare machine par nahi.
Agar zyada use karna hai to sandbox docs ka security section ek baar parhein.

Merge ka ikhtiyar insaan ke paas hai

Cloud aur sandbox Claude ko chalane mein tez aur safe banate hain. Yeh aap ke liye code review nahi karte. Har branch PR ban kar wapas aati hai jise aap parh kar merge karte hain.

05Self-check

Un-sandboxed “safe” kabhi zyada risky kyun?

Approval fatigue — aap prompts parhe baghair autopilot par stamp kar dete hain.

Plain Windows par abhi kaunsa approach nahi chalta?

Native /sandbox — filhaal WSL chahiye.

`&` task ke saath cloud mein kya jata hai?

Poora conversation context, is liye remote Claude be-rukawat jari rehta hai.

Sprite par full-YOLO safe kyun?

Yeh hardware-isolated cloud box hai — is ka koi kaam aap ki machine tak nahi pohanch sakta.

✓ Ahm baatein

YOLO safe banane ke teen tareeqe: Blue (local /sandbox), Purple (managed cloud), Yellow (Sprites).
Is bunyaad par chunein ke kaam kahan chalana hai aur parallelism ya mobility chahiye ya nahi.
Deny-rules rakhein, allow-list mehdood rakhein, keys bachayein — aur PR hamesha review karein.
Course ka 80% mukammal hai. Kal: big codebases, phir frontier — Agent SDK, Cowork aur OpenClaw.