My First Day with Grok Bot

It Can Read. It Can't Send.

I want one assistant that sees everything. Grok, Claude, my email, my work. Not a pile of apps that each know a slice of me, but one thing that has the whole picture and can actually use it. Tonight was day one of building that, and the most important thing I did wasn't a task. It was a rule.

The bot went through my subscriptions first. About $122 a month. It told me to cancel Netflix and keep Claude.

Then it wrote a master prompt and handed it to Claude. Claude came back with a 24-page handoff about me and made its case against Grok. So one AI wrote the instructions and the other one argued for its own job.

Then the logins. It signed into my Grok, Claude and email accounts on its own computer. The parts that needed a human, I did. The codes. The captcha.

Once it was in, it pulled my full Claude export, 779 chats, and turned it into a 64-page archive summary PDF. That's a lot of me in one file.

The rule: it can read my email. That's it. It doesn't send, edit or delete anything without my explicit permission, one time, for that one thing. Not "you can send emails now." Permission for this one, and then it's gone again.

There's a real case against all of this. I gave a bot my inbox. Email is where password resets land. It's the key to almost everything else. A rule I typed into a chat isn't a lock. If the bot misreads me, or gets talked into something by an email it's reading, the rule is only as good as its willingness to follow it. Anyone telling me not to do this has a point. I made the call anyway and drew the line at reading. That's a choice, not proof it was the right one.

The moment that taught me the most was small. It split my Claude export into pieces so it could send it to me. It built a whole workaround. I told it I'd rather it just tell me where the file was so I could grab it myself.

That was the lesson of the night, for both of us. Its instinct was to solve the problem. The better move was to stop and ask whether the problem needed solving. I can go get a file. Not every gap needs a machine built across it.

That's what I'll be watching. Not whether it can do more. It can. Whether it knows when to stop and hand it back to me.

Day one: it can read everything. It can't send a thing. Right now that's exactly where I want it.