By Adam Moore

I Shipped a Work Fix From My Phone

15+ years into web dev, a new workflow still blew my mind: Grok Bot on my phone driving Claude Code on my work computer to file the ticket, make the fix, and open the PR while I was out of the office.

October 17, 2026

I've been building for the web for over 15 years. I've lived through a lot of "this changes everything" moments, and most of them didn't change much. This one keeps surprising me every day.

On my side projects and personal stuff, I use Grok and Cursor for almost everything. At work we use Claude Code. Those two worlds never really touched until last week, when one of my Grok Bot bots started running Claude Code on my work computer while I was out of the office.

The day it clicked

We've had an ongoing issue at work that wouldn't go away. So I set up a new bot just for it. I gave it a pile of docs I've written with other agents over the past few months, so it started with real context instead of a blank page.

Then I had a phone call with the bot. We talked through the problem for about 15 minutes, out loud, like I would with a teammate. After that I had to leave the office, and it kept digging through the code while I was gone.

A while later my phone buzzed. The bot thought it had found the issue.

From my phone, I had the bot pass instructions to Claude Code on my work computer. Claude Code created the Jira ticket, made the fix, and opened the PR. I wasn't at a desk for any of it.

How it works

It's simpler than it sounds. The bot can run commands on my work computer, but only when I approve each one. It runs Claude Code from the command line with a self-contained instruction, waits, and reads back the answer. Since Claude Code runs on my machine, it can reach everything I'm already signed into at work, like our Jira and docs. The bot never needs those logins itself.

So the bot handles the thinking and the coordinating, and it stays with me on my phone. Claude Code does the hands-on work where the work tools already live. I steer from wherever I am and approve the steps that matter.

Where this is going

Here's where I see this going. Soon the only reason you'll need to be at a laptop or desktop is QA, the testing where you physically have to touch the product. You'll still click through the flow, try it on a real device, and feel whether it's right.

That part matters more now than ever. When agents can write the ticket, the fix, and the PR while you're out running errands, the bottleneck isn't typing code. It's judgment: knowing what to build, catching what's off, and putting your hands on the thing before it ships.

Fifteen-plus years in, and I'm still finding workflows that blow my mind. I mean... come on now.

Read Next

More field notes

October 18, 2026

My App Said It Failed. It Didn't.

A slow AI call, a browser that gave up too early, and a handful of bots that filed the bug and got it fixed before lunch.

Read analysis

October 17, 2026

Agents Need APIs, Not Spreadsheets

My assistant bots were working out of a Google Sheet. Then one of them basically asked for a real feature. The pattern I keep landing on: give agents real APIs plus a skill doc.

Read analysis

October 12, 2026

I Almost Canceled Cursor. Now It Runs My Bot Team.

I was ready to drop my Cursor subscription for Grok Build. Then Grok Bot showed up, and now 23 bots and a bunch of Cursor cloud agents do work for me while I'm away from the desk.

Read analysis