One Bot Per Task: Running Grokbot for Daily Operations

Key takeaways

Give Grokbot one job per bot. Cheng uses uncreative names and a separate bot for each task, including a chief of staff, rather than one assistant that does everything.
If you are not a developer, prefer Grokbot’s UI over living in Cursor. Cursor can still run on the backend; the point is that you do not have to see repos, commits, or the code.
The morning newspaper is the worked example: a shareable bot template that pulls calendar, email, weather, and subscriptions, then prints overnight so you can start the day without opening your phone.
Import the newspaper bot from newspaper.karenx.com or from the Grokbot marketplace under the personal category (x.ai/bot/marketplace). It will ask setup questions, then scan your Wi-Fi for a printer.
Treat hardware and logins as paste-an-API-key problems. Cheng connected a Vestaboard by grabbing the key from the display’s app; the same pattern shows up in Amazon, DoorDash, and a robot pen she is still wiring up.
Build from a pain you already have — morning scroll, stolen packages, a shirt that is out of stock — not from a blank list of “AI use cases.”
Default privacy on the newspaper keeps financial figures and medical details off the page. The printer warning is the opposite: it will find a printer and print, including at work.
The weak point she wants fixed next is login lifecycle. Subscription and shopping bots keep getting logged out on the virtual machine even when she is still logged in locally.

Who this is for (and who should skip it)

This is for a founder, operator, marketer, or ops lead who wants agents on calendar, email, shipping, and a few APIs without becoming the person who commits to GitHub. Cheng is a creative technologist and filmmaker, not a professional developer. She used Cursor, hit imposter syndrome when it asked her to manage repos, and moved the same kinds of projects into Grokbot because the interface “makes decisions for me and almost hides what I don’t need to see.”

Skip this if you want to read, edit, and ship all of the code yourself. Skip it if you will not connect email, calendar, a shopping login, a printer, or (for the messaging example) iMessage. The method assumes you are comfortable letting a bot act in those systems, and that you will keep a human in the loop for purchases and anything customer-facing.

Set up Grokbot with one bot per task

You are not building a general-purpose brain. You are staffing a desk.

Cheng’s rule is blunt: one bot per task, named after the task. She has a chief of staff bot, a package tracker, a reality-TV shows tracker, a back-in-stock tracker, a subscriptions canceler, and — while she was testing a template — about 30 morning newspaper bots. The names are intentionally uncreative. The point is that you can see what each bot owns.

Prepare nothing fancy. You need Grokbot, the accounts the bot will read (calendar, email, shopping, or a hardware API), and a single pain you can describe in a sentence. Good looks like a short roster, not a clever org chart: each bot has one job, one set of connectors, and a clear “done” (a printout, a Vestaboard flap, a text, an in-stock ping).

Failure mode: stuffing every workflow into the chief of staff. Cheng did not do that. The chief of staff exists; the package tracker still exists. Keep them split so you can iterate one output without breaking the others.

When to use Grokbot instead of Cursor

Cheng still uses Cursor for projects. Grokbot connects to Cursor on the backend, and you can spin Cursor agents from inside Grokbot. The decision is about where you stand while the work happens.

In Cursor she built what she calls the world’s dumbest smartphone: pick up a rotary phone, ask a question, hang up, and get the answer on a split-flap display (weather, exercise classes, and similar lookups). That project predates Grokbot. It meant wiring APIs, building a web interface, uploading things, and dealing with GitHub. She could ask Cursor to help, and it would, but she was in the code and felt like an imposter.

When she reproduced the spirit of that project inside Grokbot — package alerts onto the same kind of display — the path was: ask it to connect to the Vestaboard, paste the API key from the display’s app, wait. She describes it as about two minutes until the board started flapping. No web UI to build, nothing to commit, nothing to upload.

The coding is invisible. Like it’s no longer vibe coding, it’s just vibing.

Use Cursor when you need to see the software. Use Grokbot when the software is in the way of the idea. Cheng’s claim is qualitative, not a benchmark: she says she builds faster, builds things she could not build before, and that a simple UI accelerates ideas in a “subconscious way.” Treat that as her operating preference, not a measured result.

Build the morning newspaper bot

The newspaper is the full walkthrough of the method: a physical artifact, a long prompt, connectors, privacy rules, and a template other people can import.

What you are trying to accomplish: start the day with meetings, packages, weather, and a short reading pile — without unlocking your phone. Cheng’s trigger was morning scroll. She knows she should not open social apps with one eye still shut. She also could not resist checking whether a meeting moved or an urgent email landed overnight. The paper is meant to carry only that information. Grab it, read it, leave the phone down.

What to prepare

Grokbot, plus calendar and email access.
A printer on the same Wi-Fi. The bot scans the network and prints; you do not walk through printer settings.
Optional: the public template at newspaper.karenx.com, or the morning newspaper bot in the Grokbot marketplace (personal category at x.ai/bot/marketplace).
A wake-up time. The bot starts working about an hour before, like a newspaper alarm clock. Cheng sleeps next to the printer.

Setup flow

The template introduces itself, then runs a scripted intake. Cheng wrote this as a long prompt (she describes it as about 30 pages) with two halves: setup questions, then layout rules. You do not paste that novel yourself if you import her template. You answer the questions:

Your name. The printed paper uses your name, not hers. You cannot copy the “Karen Times”; you get your own.
Where you live, so it can pull weather and nearby events — “things around town to help you get you out of the house.”
Calendar and email, for the day’s meetings and the rest of the briefing.
Which email subscriptions and Substacks belong in the reading section. The bot goes through subscriptions and asks you to pick favorites.
An avatar. It draws you. You can add glasses, an outfit, and similar details so the comic looks like you.
Wake-up time, which sets the overnight run.

After intake, the bot lays out the paper and prints. Cheng’s friend hit the end of setup and watched it start printing unprompted.

What “good” looks like on the page

A day summary with meetings.
Packages arriving.
Today’s weather.
A reading section that quotes the subscription verbatim, then adds an editor’s summary so the paper does not run to 20 pages.
A comic about your actual day. Cheng’s print the morning of the recording covered the Uber to the event, being at the Grokbot event, and leaving — she had not planned that gag.
A crossword whose hints come from your life.

The template hosts fonts, a template PDF, and CSS on Cloudflare. When someone imports the bot, it pulls those files in the background. You click import; you do not assemble the design system.

Where this fails

Printer discovery is the feature and the hazard. Cheng did not connect a printer driver or choose settings. Grokbot saw a printer on Wi-Fi and went. If you finish setup at the office, it can print there. There are privacy settings: by default it keeps financial figures and medical details off the page. Still treat the print as public paper on a shared device.

Iterate a bot template until it looks like a product

Do not expect the first layout to be shippable. Cheng says the early newspaper formatting was ugly. She has no screenshots and does not pretend otherwise. The loop was: run it, give Grokbot feedback, run it again.

What she did in that loop:

Keep criticizing the design until the bot chose a print path. It landed on a WeasyPrint skill and CSS, and it picked fonts and other layout decisions.
Iterate until the page looked like a newspaper, not a dump of text.
Have the bot create a template PDF and a template CSS file.
Upload those assets to Cloudflare so every import loads the same files.
Bake connectors into the template so the next user installs them once and does not rebuild the plumbing.

Good looks like a bot someone else can add without knowing Cloudflare, CSS, or WeasyPrint exist. Cheng’s test was friends using it, plus her own overnight prints. The prototyping cost she actually names is volume: on the order of 30 newspaper bots while she was hammering the template.

If you are productizing a workflow for a team, copy that split: a long instruction doc (setup + rules), hosted static assets, and an import path. Do not hand people a chat log and call it a template.

Run logistics, restock, and show-tracking bots

Once the “one bot, one job” pattern is in place, Cheng’s other bots are the same idea aimed at different inboxes. Group them by function, not by how flashy the hardware is.

Use case	Bot / tool	Input needed	Output	Owner
Morning briefing	Morning newspaper bot (template)	Name, location, calendar, email, subscriptions, avatar, wake time, printer	Printed paper: meetings, packages, weather, reading, comic, crossword	You
Inbound logistics	Package tracker + optional Vestaboard	Package email account, Amazon login, DoorDash, display API key	What’s arriving today and this week; stops-away screenshot; physical “your package is here”	You
Procurement	Back-in-stock tracker	Product page, size, color	Once-a-day in-stock alert; optional auto-buy	You
Finance check	Subscriptions canceler	Logins for the services you pay for	How much you are spending across subscriptions	You
Watch list	Shows tracker	List of favorite shows	Renewals, premiere-night pings	You
Coordination	Grokbot controlling iMessage	iMessage settings plus a live order (e.g. Instacart)	Driver screenshots texted on a schedule	You, sending to someone else

Package tracker

Cheng keeps package mail on a separate email account, so she misses deliveries. The failure is specific: she is home, UPS does not ring, the box sits on the step and gets stolen. The bot checks that email about twice a day for what is out for delivery, then checks more often once something is moving. It logs into her Amazon account. When a delivery is out, it can send a screenshot of how many stops away the driver is. It also watches DoorDash so she knows when food is on the way.

She then pointed the same bot at the split-flap display in her room. In Grokbot she asked it to connect to the Vestaboard, pasted the API key, and the board started updating. Cursor had required a web interface and API work for the earlier phone project; this path did not.

Good looks like: you know what is arriving today and this week without opening the package inbox, and a physical display you cannot ignore when the box is at the door. You may still use your phone for everything else. Cheng does.

Back-in-stock and shows

The restock bot is a procurement watcher. She wanted a t-shirt in a color that was out of stock. Once a day the bot hits the site, checks size and color, and alerts. One day it fired — she thinks a return put a single item back — and she bought it immediately. You can set the same pattern to buy automatically. She was going on vacation and told it not to. Watch a few alerts before you let it spend money.

The shows tracker is a personal watch list: you name the shows, it tells you when something is renewed or premieres that night. Cheng uses it at the moment she would otherwise sit down and hunt for something to watch. For an operator, the transferable bit is the feed: one place that pushes the facts you used to go seeking.

Subscriptions canceler

This bot checks spend across subscriptions. It is also where she feels the product gap: things keep logging out on the virtual machine, while she may still be logged in on her local computer. If your first finance bot flaps, assume session drift before you assume the prompt is wrong.

Add if-then rules on iMessage

Grokbot can control iMessage. Cheng flags that this takes extra settings work; she does not list the toggles. Once it is on, you can put if-then logic on texts.

Her example: she Instacarted an item to a friend’s house, needed to tell the friend when it would arrive, and did not want to sit on the phone while she took a shower. Instacart does not let you share driver location with someone else. She told Grokbot to watch the driver, and once it was about 10 minutes away, to screenshot and iMessage that screenshot to the friend every two minutes.

Good looks like a multiplayer notification the vendor does not offer. Failure looks like a bot texting the wrong person, or texting too often, because you never specified a stop condition beyond “they’re close.” Stay in the loop for the first runs. This is the most customer-adjacent pattern in her stack even though the “customer” was a friend.

Pick automations from real pain, not a tool list

Cheng’s ideas did not come from a marketplace browse. They came from a constraint. Last year she tried not looking at screens on Saturdays — not every Saturday, but a day or two a month, Friday night through Sunday morning, no phones or laptops that could notify her (some TV was allowed). It was shockingly hard. She could not coordinate with friends, order food, or look up when the hardware store closed or when an exercise class started. Everything useful now lives on the phone.

The Saturday rule made the morning problem obvious. Days that started in a park were better. Days that started in the feed were not. She still needed overnight facts: who needs me, did a meeting move, was there an urgent email. The newspaper is a ridiculous solution to that exact gap. The rotary phone and split-flap display are a ridiculous solution to “I want an answer without opening the glass rectangle.” The package bot is a ridiculous solution to porch theft.

You identify a problem or a pain point that you have in your life and then just solve it.

Roshan’s prompt to viewers matches hers: install Grokbot, give it a problem you already have — phone use, getting outside, a crazy schedule, packages. If you have not used an agent in a while, you may not realize you can ask for that work at all.

Her next build is a robot pen that plots a full-size newspaper, connected over an API. She is still figuring that out. Use that as a reminder: ship the printer version before you buy a plotter.

Prompts, bot instructions, and workflows

Cheng did not publish the 30-page newspaper prompt. She did describe its structure and the questions it asks. The blocks below are reconstructed from that description, not copied from her file. Do not treat them as her production prompt.

Reconstructed from the speaker’s description — newspaper setup instructions:

You are a morning newspaper bot. On first run, introduce yourself, then complete setup before you ever print.

Ask, in order:
1. The user's name. Use only this name on the printed paper.
2. Where they live. Use this for weather and local events that could get them out of the house.
3. Permission to use their calendar and email for today's meetings, packages, and the rest of the briefing.
4. Which email subscriptions and Substacks to include in the reading section. Scan subscriptions and let them pick favorites. Do not include everything.
5. Avatar details so drawings look like them (glasses, outfit, and similar).
6. What time they wake up. Start building the paper about one hour before that time.

Privacy defaults: keep financial figures and medical details off the page.

When setup is complete, scan the local network for a printer and print. Do not ask for printer settings or a manual connection. Warn the user that printing will start automatically.

Reconstructed from the speaker’s description — layout and production rules:

Format the output as a newspaper, not a long email.

Required sections:
- Day summary with meetings
- Packages arriving
- Today's weather
- Reading section for chosen subscriptions: quote the source verbatim, then add a short editor's summary so the paper does not become ~20 pages
- A comic about the user's actual day, using their avatar
- A crossword with hints drawn from their life

Use a print-oriented layout (WeasyPrint and CSS). Hold fonts, template PDF, and CSS in one hosted place (Cloudflare in the original build) and load them when the bot runs.

After the user answers setup questions, produce the paper on the overnight schedule and print it.

Reconstructed from the speaker’s description — package tracker loop:

Watch the package email account about twice a day.
When something is out for delivery, check more often.
Log into Amazon as needed. When a delivery is out, send a screenshot of how many stops away the driver is.
Also check DoorDash for orders on the way.
If a Vestaboard (or other split-flap display) API key is present, push "your package is here" to that display. Do not build a separate web app.

Reconstructed from the speaker’s description — Instacart-to-iMessage rule:

Track the Instacart driver for this order.
When the driver is about 10 minutes away, take a screenshot.
Send that screenshot to [friend] via iMessage every two minutes until they have the item.
I am not available to relay updates myself.

Measurement and business impact

Cheng does not give hours saved, cost per bot, lead volume, or support-ticket cuts. Judge the stack the way she does: friction to first useful output, and whether you still have to open the phone for that one job.

Checkpoints she actually used:

Cursor path for the rotary-phone display: “quite some time,” APIs, a web interface, uploads, GitHub, troubleshooting.
Grokbot path for Vestaboard: paste API key; display moving on the order of two minutes.
Package bot: twice-daily email scans, then higher frequency when out for delivery, down to a stops-away screenshot.
Newspaper: overnight print in hand before the phone; friends reaching the end of setup and watching it print.
Restock: one alert, one remaining item, immediate purchase.
iMessage: friend received driver updates she did not have to sit and send.

The business-adjacent outcomes in her telling are speed of experimentation, access for a non-coder, and fewer “go seek this” loops. She also describes a personal cost: a manic stretch of ideas and worse sleep. That is not an ROI number. It is a signal that the UI removes enough friction that you can overbuild.

Pitfalls and guardrails

Auto-print is not a polite guest. The newspaper bot will discover a printer on Wi-Fi and use it. Finish setup on a network where a surprise print is acceptable.
Privacy defaults are not a policy. Financial figures and medical details stay off the page by default. Calendar, email, shopping, and location still flow through the bot. Do not put this on a shared printer and call it private.
Logins will rot. Cheng’s subscriptions canceler (and other login-heavy bots) lose sessions on the virtual machine. If a bot “stops working,” check auth before you rewrite instructions. She asked the Grokbot team to manage that lifecycle better.
Do not auto-buy on day one. The restock bot can purchase. She turned that off because she was traveling. Watch the alert quality first.
iMessage if-then needs a human on the first passes. Settings are extra, and you are sending to someone else. Confirm the recipient, the screenshot, and when it should stop.
Keep a human on brand and layout. The newspaper was ugly until she sat in the feedback loop. Grokbot made design choices; she did not accept the first ones.
Do not confuse “coding is invisible” with “no one is responsible.” Cursor is still on the backend. If you ship a template to other people, you still own connectors, hosted files, and what the bot prints.
Hardware is optional. Vestaboard, sleep-adjacent printers, and robot pens are how Cheng closes the loop without a phone. The same bots can stop at a message if you do not have the object.

7-day implementation plan

Day 1. Write down one pain that currently forces you into a phone or a messy inbox: overnight schedule changes, packages, a restock, subscription sprawl. Install Grokbot. Create the first bot named after that job only. Add a chief of staff bot if you want one, but do not put the job there. List the connectors you will need (calendar, email, shopping, printer, display API).

Days 2–3. Either import the morning newspaper bot (newspaper.karenx.com or the marketplace personal category) or clone its intake: name, location, calendar, email, subscriptions, wake time, privacy defaults. Run setup on a network where printing is safe. Read the first output against Cheng’s bar: meetings, packages, weather, a short reading section, nothing that should have stayed off the page. If you skip the newspaper, run the same intake discipline on your chosen bot — script the questions, then the rules.

Days 4–5. Stand up the package tracker or the equivalent logistics bot. Point it at the mailbox where tracking actually lives. Set a twice-a-day check, then more often when something is out for delivery. If you have a Vestaboard or similar display, paste the API key and confirm a physical message. If you do not, stop at a notification you will actually see. Give layout or copy feedback the way Cheng did on the ugly first papers; do not rebuild from scratch.

Days 6–7. Add one proactive watcher (back-in-stock or shows) so the stack pushes facts you used to hunt for. If you need to coordinate with another person, add a single iMessage if-then with a tight stop condition — and change the required settings before you trust it. Leave auto-buy off. If you are turning this into a template for someone else, export setup questions plus layout rules, and host static assets in one place the bot can load. Write down the login-rot problem so you are not surprised when a shopping or subscriptions bot dies overnight.

Start the day without opening your phone for the one job you automated. That is the checkpoint. Then watch the walkthrough if you need to see the newspaper, the printer, and the Vestaboard in motion — and start with one bot, not thirty.

FAQ

Do I need to know how to code to use Grokbot?

Cheng’s whole move to Grokbot is that she is not a developer and did not want to live in GitHub. She still used Cursor, but the Cursor UI made her feel like an imposter when it asked her to commit and manage repos. Grokbot, in her telling, hides what she does not need to see so she can state the outcome. You still need to paste API keys, grant calendar and email, and give feedback on bad output.

Grokbot vs Cursor: which one should I use?

Use both if you want what she uses. Grokbot can spin Cursor agents on the backend, so coding does not go away — it goes out of view. Choose Cursor when you are building something like her original rotary-phone project and expect to wrestle APIs and a web interface. Choose Grokbot when the job is “connect this display / print this paper / watch this inbox” and a long IDE session would kill the idea.

Where do I get the morning newspaper bot?

Cheng’s template is at newspaper.karenx.com. She also says it is in the Grokbot marketplace under the personal category; the URL given is x.ai/bot/marketplace. You can search for her as Karen X Cheng. Import it, complete the setup questions, and expect it to use your name, not hers.

Will the newspaper bot print by itself?

Yes. After setup it scans the network for printers and prints. Cheng did not configure printer settings or a manual connection; it saw a printer on Wi-Fi and started. Test at home. If you are at work, assume it may print on a shared device. Privacy defaults drop financial figures and medical details, but the page is still a physical object.

Do I need a Vestaboard or a robot pen?

No. Those are how Cheng gets notifications off her phone — a split-flap display for packages, a printer for the morning paper, and a plotter she has not finished connecting. The bots still work as email checkers, Amazon watchers, and alert senders. Hardware is the last mile, not the prerequisite.

Can Grokbot send iMessages for me?

Cheng says it can, after you change some settings (she does not list them). She used it to screenshot an Instacart driver and text a friend every two minutes once the driver was about 10 minutes away, because Instacart would not share location with that friend. Treat this as a permissions-heavy workflow and watch the first thread yourself.

How do I decide what to automate first?

Pick a pain that already burns you, the way stolen packages, morning social scroll, or an out-of-stock shirt burned her. Do not start by brainstorming “AI use cases.” One sentence of problem, one bot, one connector list. Add the next bot only when the first one produces something you would actually use tomorrow morning.

What should I expect to break?

Logins. Cheng’s feature request is better login management because the virtual machine logs out of services she is still using on her local machine. Design and layout also break on v1 — her newspaper was ugly until she iterated. Auto-print and auto-buy break in social ways: the wrong printer, or a purchase you did not mean to make while traveling.