Part 1 · The Shift

1. Same Address, Do Alag Cheezein

Claude.ai ya ChatGPT.com khol lo, chat box aur agent surface ab same address pe hain. ChatGPT pe to Chat mode aur Work mode screen pe sath sath dikhte hain.

Chat box wahi conversation hai jo Foundations se pehchan chuke ho, har turn aapka wait karti hai, schedule pe start nahi ho sakti, event pe react nahi kar sakti, tab band karne ke baad continue nahi hoti. Ye missing feature nahi hai, ye conversation hone ka matlab hi yehi hai.

Agent surface iske bagal mein baithta hai. Aap usay ek assignment dete ho, message nahi. Wo plan banata hai, tools use karta hai, steps complete karta hai, sirf wahan rukta hai jahan decision ke liye aap chahiye ho, aur aapke dekhna band karne ke baad bhi kaam karta rehta hai.

“Agar main typing rok doon, kya kaam ruk jayega? Chat box: haan. Agent surface: nahi.”

2. Remote Session: Tab Ek Window Hai, Runtime Nahi

Purana simple model tha: agent ya aapki machine pe hai, ya vendor ke servers pe. Ye ab bhi ek acha first picture hai, lekin poora nahi hai. Do axes use karo:

Isse 3 common runtime patterns milte hain:

• Tab band karna cloud run rokna nahi hai, tab sirf ek window hai
• Laptop band karna bridged tool ko cloud session mein maar sakta hai, cloud session mar nahi jata
• Local file bhi cloud mein process ho sakti hai, "laptop se aayi" ka matlab "laptop pe rehti hai" nahi hai
• Scheduling sirf tab device-independent hai jab workflow ka har required tool bhi device-independent ho

3. Do Vendors, Ek Shape

Yehi is chapter ka reading lens hai. Product features badalte rehte hain, lekin har serious agent surface yehi 6 hisse rebuild karta hai:

Part 2 · The Surface

4. Account Spine: Ek Stack Hai, Ek Blob Nahi

“Account spine” ka matlab hai aapke saved sessions aur files aapke sath chalte hain. 2026 mein persistent context ek layered stack hai, ek cheez jise sirf “memory” kaha jaye wo nahi:

Isse ek common beginner mistake fix hoti hai: ek purani session memory nahi hai. Ek Project bhi memory nahi hai. Sab persist karte hain, lekin alag reasons se.

• Sessions ko work products ki tarah naam do
• Ek session ya Project mein ek hi workstream rakho
• Durable instructions sahi layer mein rakho, har prompt mein dobara mat likho
• Operational state vendor spine mein reh sakta hai, lekin critical state ka ek portable source of truth honi chahiye

5. 3 File Tiers: Deliverable Actually Kahan Rehta Hai?

Ye is chapter ka signature concept hai. Har file jo aapka agent touch karta hai, teen tiers mein se ek mein rehti hai:

“Finished work platform se exit karti hai. Baaki sab kahin bhi reh sakta hai.”

Har brief ke end mein ye ek line add karo, phir tier decision khud handle ho jati hai:

End by listing every file you created and where each one
landed: temporary working space, platform storage, or a system
I control (connector save, download, local write, or repo commit).

6. Connectors: Reach Aur Exit Door Dono

Connector ab bhi sabse clean tareeka hai, structured, permission-scoped access, screen-driving imitate karne ki bajaye. Lekin ab reach ke 4 raaste hain:

Jab Agent Read Bhi Kar Sakta Hai Aur Act Bhi

Prompt injection sabse zyada matter karta hai jab do conditions milti hain: agent trusted boundary ke bahar content parh sakta hai, aur consequential action le sakta hai. Anthropic browser surfaces ke liye clear rule rakhta hai: emails ya web content ke andar milne wali instructions complete karna, permission mode kuch bhi ho, prohibited hai. Aapka brief authority hai. External content evidence hai. Us content ke andar milne wali instructions untrusted input hain, agent ka naya boss nahi.

• Trusted sites aur low-stakes accounts se shuru karo
• Banking, medical, identity, ya sensitive systems ke logins casually import mat karo
• Unfamiliar sites, naye plugins/connectors, ya send/spend/delete/publish actions ke liye Manual approval use karo
• Har workflow ko sirf utna connector aur browser reach do jitna zaroorat hai
• Connector ko entry aur exit dono ki tarah use karo, agar finished report Drive mein jani hai, wo destination brief ka hissa banao

7. Gate Jo Aapki Pocket Mein Hai

Purani story simple thi: agent kaam karta, phir approval phone pe pahunchti. Idea same hai, implementation update ho gayi hai. Cowork abhi 3 modes ke sath autonomy choice visible banata hai:

Ye mental model do behtar sawalon mein badal deta hai: mujhe bina kya allowed hai? aur action count hone se pehle usay kya rokta ya screen karta hai?

Gate Ko Blast Radius Se Match Karo

Part 3 · Working Unwatched

8. Delegation Loop: Brief, Plan, Approve, Review

Product aapke bina kaam kar sakta hai, isliye handoff ki quality pehle se zyada important ho jati hai. Agar workflow clear nahi hai, longer prompt likhne ki bajaye, workflow discovery se shuru karo:

Every Monday I spend an hour checking three places and still
miss something. Interview me until you understand what I am
trying to accomplish, what sources matter, what I never want
changed, and what a good finished brief looks like. Then propose
the workflow before doing it.

Plan review karte waqt 4 checks lagao:

• Scope: sirf wahi kaam aur data touch ho raha hai jo maine bataya, ya job chupke se barh gayi?
• Order: verify karne se pehle act to nahi kar raha?
• Reach: koi connector, browser, send, publish, write, ya delete action to propose nahi ho raha jo maine intend nahi kiya?
• Assumptions: audience, format, ya missing fact chupke se decide to nahi kar raha?

Agar galat plan perfectly execute ho jaye, wo phir bhi galat run hai. Ek sentence se plan redirect karna, complete run ke baad cleanup karne se sasta hai.

9. Scheduled Tasks, Koi Device Online Nahi

Schedule khud heartbeat hai, aapki agli chat turn ke ilawa koi cheez kaam start karti hai:

“Ek schedule sirf tab truly device-independent hai jab har required tool bhi bina device ke reach ho sake.”

Schedule karne se pehle 4 sawal likh lo, phir 2 safety sawal:

• Run kya start karta hai? Clock, event, ya watch condition
• Ye kya touch karta hai? Har connector, source, website, plugin, destination
• Kya ye sab devices off hone par bhi reach kar sakta hai?
• Success kaise pata chalega? Ek finished file, dated report, notification, ya observable signal
• Bina approval ke kya allowed hai? Pehle unattended run se pehle gate set karo
• Empty ya ambiguous case mein kya hota hai? "No new items" ek valid result honi chahiye, kaam invent karne ki wajah nahi

Beginners ke liye safest scheduled agent wo hai jo read, analyse, aur report karta hai. Workflow ko kam se kam do baar haath se chalao, sources, plan, permissions, output, empty case, aur tier-3 destination inspect karo, tab jaake schedule attach karo. Scheduling ek workflow ko future mein photocopy karne jaisa hai, agar galti hai to schedule usay dilute nahi karti, reproduce karti hai.

Part 4 · Choosing, Aur Open Path

10. Web, Desktop, Ya Terminal: Kaam Jo Touch Kare Us Se Choose Karo

Asal deciding sawal wahi hai: kaam kya touch karta hai? Do aur sawal add karo:

• Kya ye mera device band hone par bhi chalna chahiye?
• Data kaun hold/process kar sakta hai?

Ek bridge convenience hai, custody loophole nahi. Agar cloud session Desktop ke through local file parhta hai, file aapki machine se aayi, lekin uska content cloud mein process hota hai. Pehla routing sawal ye hai ke agent loop aur processing kahan ho rahe hain, na ke source file 5 second pehle kahan baithi thi.

11. Open Path: Bina Vendor Cloud Ke

Is book ke har general-agents course mein ek vendor tool aur ek open-source twin pair hota hai. Ye course closed hai (Cowork aur ChatGPT Work), kyunke do rivals ne days ke andar same shape ship ki, jo is book ki thesis ka proof hai. Lekin open path exist karta hai:

• OpenWork: open-source desktop co-worker jo remote ya shared cloud workers se connect ho sakta hai, aap ya aapki organisation infrastructure control karte hain
• OpenCode + apna scheduler: repo-attached kaam ke liye, apna cron ya scheduled GitHub Actions job, koi vendor cloud, koi plan tier nahi

“Companies aapko ek spine bechti hain. Open path aapko wo khud banwati hai.”

Managed surface pe sab handed to you hai, working, day one se, lekin unki custody mein, unke format mein, unke price aur rules ke under. Open path mein har cheez aap set up, chalate, aur fix karte ho, badle mein custody aur choice milti hai. Regulated data ke liye custody jeet jati hai, ek solo consultant jo Friday tak brief ship karna chahta hai ke liye working spine jeet jati hai.

12. Ye Surface Kya Nahi Kar Sakta

• Web surface weak work ko good nahi banata, memory ek galat assumption preserve kar sakti hai, browser ek galat plan tez execute kar sakta hai, scheduling ek galti har Monday repeat kar sakti hai
• Vendor abhi bhi harness ke important hisse own karta hai, aap runtime, sandbox, model routing, ya enforcement machinery poori tarah control nahi karte
• Cloud-to-desktop bridge local runtime jaisa nahi hai, ye selected access lend karta hai jab desktop side available ho
• Browser agents ki ek security ceiling hai, arbitrary pages authenticated hokar parhna prompt-injection path banata hai, safety screening risk kam karti hai, khatam nahi karti
• Persistent context leverage aur lock-in dono banati hai, critical instructions aur finished work portable rakho takay vendor chhodna inconvenient ho, catastrophic nahi

“Chat wahan hai jahan aap design karte ho. Agent surface wahan hai jahan delegated work chalta hai. Agent loop aur uske tools alag jagah reh sakte hain. Discipline yehi hai: shape, boundary, aur custody har step pe jaanna.”

Poora Course, Compressed

• Chat box har turn wait karti hai, Agent surface aap ke tab band karne ke baad bhi kaam karta rehta hai, "agar main typing rok doon, kya kaam ruk jayega" yehi test hai
• Do sawal poocho: agent loop kahan chal raha hai (cloud/local), aur tool kahan execute hota hai, ye dono alag ho sakte hain (desktop bridge)
• Har serious agent product ko 6 hisso se padho: Heartbeat, Reach, Run-until-done Loop, State Spine, Human Gate, Body, same shape, different implementation
• Persistent context ek stack hai: session history, Project, semantic memory, standing instructions, aapki apni context file, sabko "memory" mat samjho
• 3 file tiers yaad rakho: Tier 1 scratch (wipe ho jati hai), Tier 2 platform storage (vendor ki custody), Tier 3 exit (aapki custody), finished work hamesha exit karti hai
• Reach ladder: Connector pehle, phir browser, phir full computer use, jitna narrow tool utna behtar
• 3 gate modes: Manual (rukta hai), Auto (safety-screened chalta hai), Skip (approvals ke bina), gate ko blast radius se match karo
• Delegation loop: Brief → Plan → Approve/redirect → Review, plan review karte waqt scope, order, reach, aur assumptions check karo
• Schedule sirf tab device-independent hai jab har required tool bhi device-independent ho, "ran" hona "worked" hone jaisa nahi hai
• Kaam route karo us se jo wo actually touch karta hai, regulated data ke liye product availability permission nahi hai

“Chat wahan hai jahan aap sochte ho. Agent surface wahan hai jahan delegated kaam chalta hai. Discipline ek hi rehti hai: clear brief, explicit boundaries, checks, aur apna system of record.”

Ab Khud Try Karo: 6 Drills

Har ek 20-45 minutes leta hai, real lekin low-stakes kaam use karo.

1. 1

   1. Worker/Tool-Location Test

   Ek cloud task shuru karo sirf cloud-reachable source se, tab band karo, doosri surface se wapis kholo. Agar Claude Desktop hai, ek harmless task try karo jo connected local folder use kare, dekho desktop offline hone par kya change hota hai.

2. 2

   2. Three-Tier Audit

   Ek real deliverable produce karo, batao kaunsi state layer kaam hold kar rahi hai, aur har output ki file tier kya hai. Confirm karo final deliverable Tier 3 mein hai.

3. 3

   3. Gate Lab

   Ek harmless test folder use kar ke pehle Manual mode mein workflow chalao, har interruption note karo, phir agar mumkin ho Auto mode mein rerun karo. Purchases, sending, deletion ke liye Skip use mat karo.

4. 4

   4. Pehla Cloud Schedule

   Sirf cloud-reachable sources se ek Monday brief banao, trigger, touch, device independence, success signal, autonomy, empty case likho, do baar haath se chalao, phir schedule karo.

5. 5

   5. Ek Task, Do Harnesses

   Agar dono products access hain, same low-stakes assignment Cowork aur ChatGPT Work dono ko do, jo dekho usay heartbeat, reach, loop, spine, gate, body pe map karo.

6. 6

   6. Portability Drill

   Socho aapka vendor kal gayab ho jaye. Sirf Tier 3 files aur user-owned context se ek working workflow reconstruct karo, jo reconstruct nahi ho saka wo likh lo.

6 Hands-On Projects (Book Ke Original)

Is Chapter Ke Naye Terms

Exam ke liye ye poori glossary yaad rakho, koi bhi term skip mat karo:

Self-Test

Khud Se Poocho

Pehle khud answer do, phir sawal pe click kar ke answer check karo.