Third-party cloud sandboxes: Sprites.dev
Naya aur pioneering tareeqa: Anthropic ka cloud bilkul use na karein — third party se specialist sandbox rent karein. Hum Sprites.dev (fly.io team ka) use karenge: persistent Linux box jo ek second se kam mein boot hota aur kisi bhi coding agent ko full YOLO mein chalata hai, kyun ke us ka koi kaam aap tak nahi pohanch sakta.
Yeh teesra approach optional hai — ho sakta hai aap native sandbox aur Anthropic cloud se khush hon. Phir bhi dekhna worth it hai, kyun ke cheezen isi taraf ja rahi hain aur yeh sirf Claude nahi balki kisi bhi agent ke saath kaam karta hai.
01Third-party sandbox kya hota hai
Anthropic ke box host karne ke bajaye doosri company aap ko hardware-isolated cloud container deti hai jo coding agents ke liye tayyar hai. Sprites.dev apne aap ko “stateful sandbox environment with checkpoint and restore” kehta hai — persistent Linux computer, jo is sawal ka asaan jawab hai: “is code ko kahan chalana chahiye?”
Ek second se kam
fly.io boot speed par fakhr karta hai — sprite create taqreeban 0.6s mein wapas aata hai. Server install hone ka intezar nahi.
Ghar se door ghar
Checkpoint aur restore: baad mein wapas aayein to sab bilkul wahi hota hai. Aap ka remote dev box hamesha tayyar.
Waqai sandboxed
Hardware-isolated. Full YOLO mein chalayein — jo chahe kare, aap ki machine tak kabhi na pohanche.
02Sign up aur CLI install karein
Sprites.dev par account banayein
~$30 trial credit (“500 sprites free”) mil raha tha. Free credits ke bawajood credit card maangta hai — aage barhna ya sirf dekhna aap ki choice hai.
Sprite CLI install karein
Pehli screen par aap ki key shamil one-line install command hoti hai. Kisi bhi terminal mein paste karein.
Log in karein
sprite login browser khol kar isi account se sign in karata hai. Ab sprite command tayyar hai.
Sign-up aap ko fly.io ke page par le jata hai (Sprites fly.io ne banaya hai) — Sprites.dev par wapas aayein aur login ho jayega. Aur install command kabhi share na karein: is mein aap ki key hoti hai.
03Sprite banayein aur repo clone karein
Yahan yeh itna asaan hai ke lagbhag mazaaq lagta hai:
sprite create finally-worker Created finally-worker in 0.6 seconds. # the prompt changes to sprite@sprite — you are now ON the remote box sprite@sprite:~$ ls # empty — a fresh cloud machine sprite@sprite:~$ git clone <your finally repo> sprite@sprite:~$ cd finally && ls backend CLAUDE.md LICENSE planning README.md
sprite@sprite batata hai ke ab har command cloud ke remote box par chalti hai — chahe local terminal jaisi hi nazar aaye (khaas taur par VS Code terminal mein).
04Claude ko safe YOLO mein chalayein
Har Sprite par Claude Code pre-installed hota hai. Sirf claude type karein.
sprite@sprite:~/finally$ claude # first-run questions (dark mode, etc.), then it wants to log in. # Press 1 — it opens the browser on YOUR laptop, you authorise, done. # It boots in "bypass permissions" (YOLO) mode automatically: ⚠ Claude Code running in bypass-permissions mode. Yes, I accept. # Safe — it’s an isolated cloud box with a public repo. Nothing can hurt you.
Naya box thora purana Claude Code chala sakta hai (misal ke taur par purane model par). Bas quit karke claude dobara launch karein — yeh khud latest version aur model par update ho jayega.
Ab isay real kaam dein — sab kuch remotely chalega jab aap ka laptop khaali hoga:
> Read all docs in planning/. The market-data backend is implemented with tests. Carry out a comprehensive code review, run all the tests, and write your conclusions to planning/market-data-review.md
05Poora remote workflow
Neeche wala loop poora jadoo hai — remote box ko local ki tarah chalana:
Run review karein
Ctrl+O poori conversation dikhata hai — misal ke taur par aksar tests pass, kuch fail aur Claude ne sab ka hisaab diya.
Box se GitHub login karein
Push karne ke liye gh auth login chahiye. Box remote hone ke bawajood auth window aap ke laptop par khulti hai. Login ke baad claude phir /resume type karke wahi se jari karein.
Push aur PR kholne dein
“Main ne aap ko login kar diya — ab koshish karein.” Yeh branch banata, push karta aur PR kholta hai. GitHub par review aur merge karein.
Hands-off jari rakhein
“Ab main par switch, pull, review file ki har cheez theek karo jab tak tests pass hon, phir nayi branch push karo.” Yeh baghair approvals kaam karta aur doosra PR deta hai.
Tajurba dono duniyaon ka behtareen mel hai: bohot productive (permission ki tang nahi) aur bilkul secure (fully sandboxed). Isi combination ki wajah se yeh itna khushgawar hai.
06Har agent ke liye kaam karta hai
Aakhri baat: Sprite ko farq nahi padta aap kaunsa agent chalate hain. Claude Code, Codex, OpenCode — jo bhi chunein, sandbox mein chalane ke liye ideal hai. Isi platform-independence ki wajah se third-party sandboxes mashhoor ho rahe hain.
✓ Ahm baatein
- Third-party sandbox coding agents ke liye rented, hardware-isolated cloud box hai — misal Sprites.dev.
- Yeh tez (<1s mein create), stateful (wahi se resume) aur isolated (safe full-YOLO) hai.
- Flow:
sprite create→git clone→claude(pre-installed) → kaam →gh auth login→ push → PR. - Box remote hone ke bawajood login aur auth windows aap ke laptop par khulti hain.
- Yeh agent-agnostic hai — is ke andar Claude, Codex ya OpenCode chalayein.