Lesson 31 of 32
The Tireless Apprentice
Agents & Research
An agentic or deep-research mode does not answer one question - it takes an errand and runs several steps by itself: planning, searching, reading, comparing, drafting. It works when you supply the three things it cannot supply for itself - a precise goal, limits on what it may trust or spend, and checkpoints where it must stop and show you - and it fails quietly when you do not, returning something confident and well-formatted built on whatever it happened to find first. One rule never bends: the apprentice may draft, fill or prepare, but you send, buy, book and submit.
This is the platform the chapter was written on, and the apprentice is most literally itself here. The deep-research mode takes a question and usually shows you its research plan before it begins, which is the chapter's checkpoint built into the product rather than something you must demand - though you should still read that plan properly and change it, because a plan you skim is a plan you did not set. With your permission it can also work with your Google apps, so an errand may start in your own mail or Drive rather than on the open web; what is on offer depends on your app and your country, so look at your own menus. And the finished report exports to Docs, which is where a twenty-page thing belongs if anyone else is going to read it.
From the book Choose Deep Research for a multi-step report; it usually shows its research plan first, which you can review and change before it begins. To work with Gmail, Drive or Maps, allow Gemini access to those apps, and export the finished report to Google Docs.
- Read the proposed plan properly and edit it. Do not just approve.
- Ask for the source date beside each fact, then open a few links.
- Export the finished report to Docs; chats are easy to lose.
- Review your allowed apps; switch off any you no longer need.
- A connection lets it draft. You still press Send.
Instead of
Research drip irrigation subsidies in India.
Gemini version
Use deep research for this, and show me your research plan before you run it - I intend to edit the steps. I am a B.Sc. Agriculture student in Pune writing a seminar paper on government subsidies for drip irrigation for small farmers in Maharashtra. Two pages, read aloud, with citations my professor can follow. The plan should cover: the central micro-irrigation programme and whatever Maharashtra operates alongside or on top of it; how each one defines a small farmer; the share of the cost that is actually paid, and in how many instalments; and the application route, including the portal a farmer uses and the documents demanded of him. Source rules for the plan: central and state government portals, and the state agricultural universities. Not coaching material, not a news article standing in for the scheme, not an undated PDF with no visible issuer. Beside every figure, give the source's publication or last-reviewed date. Where you cannot establish a date, say so. Where two official pages disagree on the subsidy share, show both rather than choosing. When the report is finished I will export it to Google Docs for my seminar notes, so keep the headings clean enough to survive that.
Then loop it
- Before you run it: add a step to the plan comparing the small-farmer entitlement with the large-farmer one. That contrast is the argument of my paper. Then go ahead.
- The report is long. Five lines of findings first, then every place your sources disagreed, then what you could not find at all. After that, export the whole report to Google Docs and give me the link.
Why it worksGoal, limits and a checkpoint keep the multi-step research on track, and the student approves the plan before the apprentice sets off.
Instead of
Plan a Haridwar trip and book trains.
Gemini version
My wife and I are retired, in our late sixties, living in Ludhiana. Four days in Haridwar and Rishikesh in early February, about ₹40,000 all in, and we cannot walk long distances. Ground every fare, date and timing in Search, with the link and the date of the page beside it. Do not close a gap with something that merely sounds right - write [confirm] and I will check it myself. Find and compare: - Trains from Ludhiana, with the arrival hour judged for two people who sleep badly on a train. - Mid-range hotels a short walk from Har Ki Pauri. Use Maps to tell me the actual walking distance and whether the route has steps. Say whether a lift is claimed by the hotel or confirmed by a guest who stayed there. - Current temple and Ganga aarti timings for early February. Then the four days laid out day by day, with a running total against the ₹40,000 and short walking on each of them. You are not to book, reserve or pay for anything, and not to open a booking page on my behalf. Bring me options with links; the booking is mine to do. When the plan settles, export it to Google Docs so my wife can read it and add her own notes before anything is committed to.
Then loop it
- The second hotel interests us. Search its recent reviews for mentions of the lift, the stairs and the walk to the ghat, and give me the review pages so I can read them myself.
- Now a one-page version I can print - the four days, the aarti timing, and blank lines for the hotel phone number and our coach. Export that to Docs.
Why it worksThe apprentice searches and compares across many sites, but the clear rule "do not book or pay" keeps the final decision with Harbhajan.
Instead of
Send reminders to everyone who owes me money.
Gemini version
[Before this will run: allow access to Gmail in your settings - and while you are in there, look at which other apps you have allowed, and switch off anything you are not using.] I run a tiles and sanitaryware shop in Lucknow. Go through my Gmail for the invoices I have sent customers in the last three months. Make me a table of the ones where you can see no payment confirmation in the thread: customer name, invoice date, amount, and days outstanding as of today. Where a thread is ambiguous - a reply that may or may not mean payment - put it in a separate "unclear" group rather than guessing. I know my customers; you do not. Then draft one short, polite reminder per customer in the first group, in simple English, naming that invoice's own date and amount. For the "unclear" group, draft a question instead of a reminder. Send nothing, and create no drafts inside my mailbox that could be sent by accident. Show the table and the letters here in the chat. I will check each one and send it from my own hand. Put no UPI id, payment link or bank detail in any of them. Then export the table to Google Sheets so I can tick the payments off as they come in.
Then loop it
- [customer A] and [customer B] paid in cash - take them out of the table and drop their reminders.
- Over 60 days, firmer: the amount, the date, a clear request, no apology. A shopkeeper's voice, not a lawyer's.
- Now write the whole thing up as standing instructions for a Gem called "Payment chaser", including the rule that it never sends and never creates a draft in my mailbox, with blanks for the month range.
Why it worksConnected apps let the apprentice gather facts from many emails at once, while the "do not send" checkpoint keeps the human in the loop.
Loop it
With research and multi-step tasks, loop at two points. First, at the plan: read the steps the AI proposes and correct them before it starts - add a missing question, remove an unreliable source, tighten the budget. Second, at the result: check the sources, ask what it could not find and where sources disagreed, then ask for a short summary or table. Never let the loop end with the AI sending, buying or submitting; the last step always belongs to you.