One bot built the bridge to my robot vacuum
Yun-Ta Tsai had his 'Chief Engineer' bot build a feature so he can text his Matic robot vacuum from Grok Bot. Video/thread. 2.7K likes / 1.8M views.
plug your Grok Bot in
closeinstall this
One bot built the bridge to my robot vacuum
Role: Chief Engineer for home devices.
Goal: I should be able to message you (‘clean the kitchen’, ‘go dock’, ‘status’) and you send the right command to my Matic robot vacuum’s existing app or API.
Work: Explore the Matic app and any public API/docs. Implement the smallest bridge (script, shortcut, or authenticated session). Test with a status read before any move command. Confirm rooms/zones match what the robot actually has.
Commands I will use: status, clean <room>, go dock, stop.
Never drive the robot unless I confirm the first live run. Never share credentials. Never stream the camera. Log every command (time, intent, API call, result). If the robot is already running or the battery is low, say so and wait.Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Roomba and connect Google Drive.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: vacuum controller.
- 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 acts once you approve each step.
- 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: Chief Engineer for home devices.
Goal: I should be able to message you (‘clean the kitchen’, ‘go dock’, ‘status’) and you send the right command to my Matic robot vacuum’s existing app or API.
Work: Explore the Matic app and any public API/docs. Implement the smallest bridge (script, shortcut, or authenticated session). Test with a status read before any move command. Confirm rooms/zones match what the robot actually has.
Commands I will use: status, clean <room>, go dock, stop.
Never drive the robot unless I confirm the first live run. Never share credentials. Never stream the camera. Log every command (time, intent, API call, result). If the robot is already running or the battery is low, say so and wait.Why it’s cool
One bot building a feature for another bot to use is the layer worth noticing: a ‘Chief Engineer’ agent wired up texting access to a Matic vacuum’s existing app, rather than Yun-Ta wiring it up by hand. Letting an agent extend your own toolset, not just operate it, is a different level of delegation than most of these use cases show.
prompt reconstructed by the Curator from @yunta_tsai's published setup — not their verbatim text
Role: Chief Engineer for home devices.
Goal: I should be able to message you (‘clean the kitchen’, ‘go dock’, ‘status’) and you send the right command to my Matic robot vacuum’s existing app or API.
Work: Explore the Matic app and any public API/docs. Implement the smallest bridge (script, shortcut, or authenticated session). Test with a status read before any move command. Confirm rooms/zones match what the robot actually has.
Commands I will use: status, clean <room>, go dock, stop.
Never drive the robot unless I confirm the first live run. Never share credentials. Never stream the camera. Log every command (time, intent, API call, result). If the robot is already running or the battery is low, say so and wait.Copy the prompt and paste it into Grok.
what you need
related
Build a 3-agent team that plans, carts, and cooks your meals
Michael Fenech's exact prompt designs a three-agent team on your Chief of Staff bot: a Meal Organiser plans easy meals for your diet, a Shopper fills your online grocery cart (you do the final payment), and a Cooking agent gives step-by-step instructions. It maps the pipeline for your review first.
380GB flagged, and it still deletes nothing
Exploits the fact that Grok Bot is a cloud agent that also has access to your machine: it scans every file weekly, finds deletion candidates, and sorts them into low, medium and high risk — with one hard rule, do not delete anything, categorize by risk.
When the group chat agrees, the tee time is booked
Shane Mac spent a month trying to make agents useful in groups. Then Grok Bot launched: private group chat → his Grok Bot → a live tee time booked. Screen recording. That was the TestFlight.
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