Skip to content
Common Sense Systems Book a free consult

Insights

I Manage a Fleet of Grok Bots Every Day Without Losing Work

By John Sambrook · · AI, Small Business, Practical Tips

TL;DR

I run a fleet of Grok Bots for my business, and they have been a success. This week I saw a post from one owner who had lost some work and was frustrated, and it made me want to share the habits I use. Know what lives where. Keep a second copy of anything that matters. When something acts up, start with the gentlest fix and save Reset for last.

Every morning my bots are already at work before I am. One writes my morning brief. One handles outbound follow-up. One helps with my networking group. One works for a colleague. The main one runs everything else: email drafts, my website, and research. Yesterday it helped me prepare for a client meeting, tracked down two of my old articles I needed for it, and added a line to my website’s robots.txt so Google’s AI tools know they are welcome.

I recognize the value of Grok Bot, and it is substantial. I also understand that people get confused at times about how it works. This week I read a post from one owner who had asked support to restore a single folder and ended up with the whole computer rolled back, losing some of their work. They were frustrated, and I understand why. Like any capable tool, Grok Bot works best when you know a little about how it is put together. Here is what I do.

What lives where

It helps to know that all your bots share one cloud computer. Grok Bot’s own documentation is plain about this: every bot on your account uses the same computer, the same files, and the same browser sign-ins. Separate bots are not separate security boundaries.

Some things are not on that computer at all. Your chat history is stored separately, so a computer problem does not touch your conversations. Your connector sign-ins, for things like Gmail and Google Drive, stay on Cursor’s servers. The documentation says those tokens “are never stored on the computer.” Keys you save through the secure secret card are kept the same way.

Your files and your browser logins are on the computer. Cursor keeps a saved copy and restores from it when the computer is updated, recovered, or reset. The help page notes that if the computer cannot be reached to save first, “very recent changes may be lost.”

Software you or your bots installed is removed when the whole computer is replaced. So are project folders like node_modules and Python environments. A key that a bot typed into a file can go too.

The security page also says that a “customer-managed point-in-time restore of an individual computer” is not available. You cannot pick a date and roll back yourself.

Knowing that, one habit covers most of it.

Keep a second copy of anything you would hate to redo

If losing it would cost you a day, keep a copy somewhere besides the bot’s computer.

For me that means code and text go to GitHub, and finished documents go to Google Drive. A full copy of the shared workspace also goes to Drive. When I checked this morning, every one of my code repositories was clean and pushed.

A Cursor support person on their own forum gave a user the same advice: if there are files you cannot afford to lose, have one of your bots send you a copy or upload them somewhere you control. When the people who run the service say that, I listen.

A backup sitting on the same computer it protects does not help much. I found one of those in my own setup this week, plus two custom bot skills that existed only on the bot’s computer. Both are on my list to fix.

Keys go in the secure card

When a bot needs an API key, Grok Bot shows a secure card. The value is masked, kept out of the chat, and never shown to the bot. Use it. Do not paste keys into chat, and do not let a bot write them into a file “to keep a copy.” The documentation says the same thing, in nearly those words.

For passwords, two-factor codes, and payment steps, take over the computer and do that step yourself. It takes a minute, and a password never sits anywhere a bot can read it.

Remember that every bot shares the browser

If you sign in to your bank on the bot’s computer for one bot, every bot can use that session. Only sign in to accounts that all your bots may touch, and sign out when a project ends. Where there is a connector for a service, use it instead of the browser. It is more reliable, and the sign-in does not live on the computer.

Keep an eye on routines

Routines are the scheduled jobs that make bots feel like staff. A few details from the documentation are worth knowing before you depend on them:

I also spread my routines out so they are not all firing at the same minute. It keeps the computer from getting crowded.

Use memory for preferences, and files for facts

A bot remembers your preferences and a summary of its past work. The documentation says plainly that “memory is not a substitute for an authoritative source.” Keep facts that change in the system they belong to, like your calendar, your books, or your customer list. Ask the bot to check the real source before anything important. The documentation does not say exactly where a bot’s learned memory is stored or how it is backed up, so anything I would hate to lose goes into a file.

When something acts up, start gently

Most hiccups sort themselves out with the first step or two. The official order is:

  1. Wait, then choose Retry. “Reconnecting” is normal, and your files are safe while it reconnects.
  2. Fully quit Grok Bot and reopen it.
  3. Check status.cursor.com. If there is a Grok Bot incident, wait for it to clear. The help pages say a Reset will not fix a service problem, so patience is the right move.
  4. Use Update Bot’s Computer in Settings if an update is offered.
  5. Use Recover if the app offers it and the computer still will not connect.
  6. Reset only after all of that, and only if you can accept losing recent work.

Two more rules from the help pages are worth writing on a sticky note. If Update says your files “aren’t ready,” do not Reset to force it. Update is waiting because it cannot make a fresh copy first, and a Reset would rebuild from an older one. And do not start a second Update or Reset while one is running.

If bots or files look missing, check another device and the hidden-bots list before you touch anything. Then email support at hi@cursor.com. Say exactly what you want in writing, for example: “please restore my files from before 3 PM yesterday, do not reset the whole computer, and confirm with me before you change anything.” Then copy your newest files off the computer before anyone does anything.

Keep an eye on the meter

Grok Bot usage is a weekly allowance, with paid extra usage beyond it if you turn that on. A spending cap is not a hard stop in the middle of a run, so a bot that is already working can go past it. Busy routines and heavy browser work use the allowance faster than you might expect. I look at usage mid-week and slow down the routines that are not earning their keep.

Keep approvals on the things that matter

My bots draft. I send. Anything that sends, publishes, buys, deletes, or changes my website waits for my yes. Grok Bot lets you add your own “ask first” rules, and the documentation recommends keeping them narrow, like “ask first before sending any external email.” Start a new job draft-only, and loosen it once it has earned your trust.

The short version

None of this is hard. It is the same discipline any small business already uses for its laptops and its books. Keep a second copy of anything you cannot afford to lose, keep passwords where they belong, and start with the smallest fix.

Grok Bot does a lot of good work for me, and a few habits let me lean on it with confidence.

It also helps to have someone in your corner. What would have helped the owner I mentioned at the start is someone who knew their setup and could have said “copy these files off first” before anything was touched. Keeping bots in good shape, and being there when one hits a snag, is now part of what I do for clients. If you run Grok Bot in your business and would like a second set of eyes on your setup, write to me at john@common-sense.com. I am happy to compare notes.

Sources

Want to talk about your own bottleneck?

The first hour is free, and you get a written proposal.

Book a free consult