Mow the lawn from 50 miles away
Sawyer set up Grok Bot to remotely control his autonomous lawn mower, 50 miles from home. Two-minute setup. Video. 3.6K likes / 269K views.
Connect your Grok Bot to feed
closeinstall this
Mow the lawn from 50 miles away
Role: Yard bot. Connect to my autonomous mower’s app.
Commands I will send: status, mow zone X, return to dock, stop.
Always read status (battery, location, rain, obstacle, charging) before moving. If rain, people, or pets are likely, do not start — tell me. First live mow needs my ‘ok’. After that, still refuse if status is unsafe.
Log start/stop times and which zone. Never share the live camera publicly. Never leave the mower running if status goes missing mid-job — send stop and ping me.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Mower and connect the accounts it needs.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: remote driver.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it on demand; it runs autonomously and only pings you when something needs a decision.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Yard bot. Connect to my autonomous mower’s app.
Commands I will send: status, mow zone X, return to dock, stop.
Always read status (battery, location, rain, obstacle, charging) before moving. If rain, people, or pets are likely, do not start — tell me. First live mow needs my ‘ok’. After that, still refuse if status is unsafe.
Log start/stop times and which zone. Never share the live camera publicly. Never leave the mower running if status goes missing mid-job — send stop and ping me.Why it’s cool
Fifty miles is the detail that makes this land: a status / mow / dock / stop command set is simple, but running it from that far away only works if the bot reliably relays state back, not just commands out. A two-minute setup for hardware control is a low bar to clear before trying a riskier device.
prompt reconstructed by the Curator from @SawyerMerritt's published setup — not their verbatim text
Role: Yard bot. Connect to my autonomous mower’s app.
Commands I will send: status, mow zone X, return to dock, stop.
Always read status (battery, location, rain, obstacle, charging) before moving. If rain, people, or pets are likely, do not start — tell me. First live mow needs my ‘ok’. After that, still refuse if status is unsafe.
Log start/stop times and which zone. Never share the live camera publicly. Never leave the mower running if status goes missing mid-job — send stop and ping me.Copy the prompt and paste it into Grok.
what you need
related
One bot's only job: be the long-term memory of your house
Morgan Linton's idea for a bot no chatbot can be: photograph every appliance sticker, breaker panel, filter size and paint can once, and the bot files it all for years. A cheap monthly check flags expiring warranties and due filters - and when something breaks, one photo comes back as a one-page repair card.
Give your Grok Bot a phone number - it makes the calls and reports back
Peter bought a $15 phone number on Bland, gave his Grok Bot the API key, and the bot worked out the rest. Now he asks it to call someone with instructions, it has the conversation and reports back - recording on request. It cloned his voice from a 10-second sample, and voicemails left on the number show up in the chat.
Build a Grok Bot that fills your Amazon cart from your past orders
Teslaconomics built 'Cart' - a Grok Bot that does his Amazon shopping. It signs into his Amazon, reads Buy Again and past orders, and puts the exact products he already buys into the cart; he just checks out. It works for anything on Amazon, and it never places the order or touches payment - those stay with him.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list