Marcos read the spreadsheet twice before he said anything. Then he said: "If we had hired someone and they did this in a month, I'd be happy." Grokbot had done it in three days.
This post is not about a company I work for. It's about Grokbot, and a few things it did that I still find hard to believe.
I had tried a lot of agents before. First OpenClaw, then ZeroClaw, then Hermes, and finally my own agents in Mastra. Each one was a little better than the last. When someone told me about Grokbot, I expected another small step. The gap was huge. Most of it is integration: the tools come integrated through simple connectors, and it works out of the box.
Give it a goal, not a plan
It started with Tute Costa. He told me he had stopped giving Grokbot implementation details. He gave it a goal, and it found its own way to the end. So I gave it access to my computers and tried the same thing with Cross Ledger, the bookkeeper placement company I run with Marcos.
I gave Cross Ledger its own bot. My first goal for it was small: help me organize my Cross Ledger work. Then I went bigger. I gave it all of Marcos's chats and emails and asked it to learn what he does. It read everything, mapped his workflow, and started doing the same. It did it faster, and it improved the spreadsheet with more information than we had collected ourselves.
We had interviewed candidates for that job. We wanted to hire someone. The bot did a month of that person's work in three days.
From there it kept going:
- It produced videos in my voice, cloned with Cartesia.
- It set up a schedule to post on Instagram and LinkedIn.
- It reached out to possible clients, and to bookkeeper candidates, by email and LinkedIn.
- It had the idea for a LinkedIn post about salaries. That post went viral. We never had a viral post before.
The salary idea was not mine and not Marcos's. That part still bothers me a little, in a good way.
Before the keys
All of this meant giving a bot my files, my accounts and a phone number that strangers can text. That is Simon Willison's lethal trifecta: private data, untrusted input, and a way to send data out. It worried me.
Then I put it to the test. A friend texted the bot, pretended to be me, and tried to get my personal information. It didn't work. Then I asked Marcos to pretend to be me and text the Cross Ledger number. He was convincing. I even gave him extra details about me to make the trick better. Grokbot didn't follow his instructions. It warned me and asked me to confirm.
It stayed safe in every test, at least for now. That's when I felt OK giving it the keys to the house.
Not every key, though. One day it found a concert and asked if I wanted it to buy tickets. I asked how it would pay, since it didn't have my cards. Or did it? It said no, it didn't, but I could save a card in its secure vault. I haven't. Yet.
The red car
Two smaller stories, because they show how it thinks.
I was in Buenos Aires with Tute, half business, half not. We were talking about racing cars, and I remembered a photo of me next to a red Formula 1 car in Germany. I don't use iCloud or Google Photos. My photos live on two backup hard drives and on my Legion laptop. Thousands of them, from before 2009 to today.
I sent one message:
Look for the photo of me in Germany with a red Formula 1 car.
It sent the photo back in a few minutes. Tute asked the right question: how did it find it, and how much did that cost in tokens? I didn't know, so I asked. Grokbot explained:
- It knew I was in Germany only in 2009 and 2023. It dropped every folder with other dates.
- It knew the car was red. It checked the remaining photos in blocks of a hundred and dropped every block with no red in it.
- It looked at the few photos left, one by one.
It called this the fast and cost-effective approach. It didn't look at every photo. It used what it knew about me to make the search small first. That's what a good engineer does with a slow query.
My face at the gate
In my gated complex, the entrance has face recognition. My face was never in the system. So I used a card, or I called the guards. Some days I forgot the card and the guards were away, and I waited.
For months I asked the guards, the owner of the apartment I rent, and the building administrator how to get my face registered. Nobody knew. Every answer was "they're coming soon, I'll tell you."
I told Grokbot. I had given it my American WhatsApp number, so it could send messages. It found the company that runs the system and wrote to them. That company said it was another company's job. It wrote to the other company, found out what they needed, and handled the request. Then it asked me for one thing: photos of my face and my girlfriend's face.
I took the photos and sent them. That was my whole part.
Next: code
The next step is code. Tute already uses Grokbot as a code orchestrator. I haven't yet, but I'm setting it up now. He runs one bot for all his projects, and that fits his setup. Mine is different. Sergio is my orchestrator, and 19 other bots each own one project or one set of tasks. That's why I want one code bot per project too.
The setup: the bot reaches my machines over my Tailnet, runs Claude Code inside Herdr, uses my Claude skills and our workflows, and opens PRs through a GitHub connection.
I know how this goes, because it went the same way at RailsPilot. The first tasks need a lot of my hands and a lot of corrections. Each correction goes into a skill. My Figma fidelity skill, for example, compares the app against the Figma frames, and it gets better every time I correct it. Each iteration, the bot does more and I do less.
That only holds for repetitive tasks: notifications, design passes, the same kind of request again. And a lot of what we do is like that. The goal is to start that process from wherever I am, with one message, and come back only to review the code.
What changed in how I work
- Give the goal. Leave out the steps, then ask how it did it. You learn from the answer.
- Give it real access: files, accounts, a phone number. Most of the value is behind that access.
- Before you give it access, attack it. Ask people you trust to pretend to be you.
We interviewed people for the job Grokbot ended up doing. None of them had to get past my co-founder pretending to be me.
I'm Fred Sapuppo, a Rails developer in Alta Gracia, Argentina. I run crossledger.net and build at fedesapuppo.com.