On my last long drive I worked for about an hour and a half, by voice only. I talked to Grok Bot, Grok Bot talked to my T3 Code threads, and I got more done than on a normal day at the office. Since then I use the same setup at my home desk.
In the video I said the setup details would be in a blog post. This is it: both versions I've used (the five-minute one and the Tailscale one I use now), with the pitfalls I hit. You can also give this page to your own agent and let it help you set it up.
The setup at a glance
- Grok Bot is the voice. I talk to it, and it comes back to me when a thread has a question or is done.
- T3 Code runs my coding agents as threads.
- The god thread is one thread per project that talks to all the other threads on it. Grok Bot only talks to that one.
- The connection between Grok Bot and T3 comes in two versions. The easy one lets Grok Bot run the
t3command on your PC. The better one puts Grok Bot's computer on your Tailscale network and lets it talk to T3's MCP.
Why Grok Bot
I had to visit another city every day for four days. The drive is about an hour and a half each way, so that's three hours in the car a day and twelve hours in total.
The first day I had long calls on the way there and back. After that it was music and podcasts, and that got old fast. I wanted to get work done on aicms, one of our products, and I needed something I could use with my voice only, so my eyes stayed on the road.
Most of the big labs have a voice bot for this now. The problem is where they work. Claude Duet is US-only (a preview for Pro and Max). OpenAI Dots excludes the EU, the UK and Switzerland. Meta Muse is US and Canada only, and Gemini Spark isn't in the EU either.
Grok Bot is the only one that worked for me here in Romania. (xAI doesn't say officially where it's available.) I was already using it every day, because I have it check X for AI news. Say what you want about X, when something happens in AI, it's trending there pretty fast.
How it worked: one god thread
When I work on something I usually have five to ten threads open, each on its own task. After a while it's hard to keep track of which one is waiting for me, which one I need to answer, and what matters most. So I keep one main thread, which I call the god thread. I only talk to that one, and it figures out what to send to the others so they get unblocked. I showed it in section 9 of my T3 Code setup post.
In the car, Grok Bot talked only to the god thread for aicms. Quick background: we mostly build large B2B software, but most of our clients still have a marketing website, and some of those run on WordPress. We don't want to maintain those, so we built aicms to replace them. It's a website builder with a lot of AI features, and with what we've learned about building good websites built in.
Here's an example of what I told Grok Bot while driving:
Tell the aicms thread to start a new thread for the newsletter module: research what important features we're missing, and definitely add auto-unsubscribe when an email bounces or gets a spam complaint.I added that newsletter module a few weeks ago, when I needed one for my own weekly email.
Grok Bot passes the message to the god thread, which starts the new thread. Grok Bot keeps an eye on the threads, so when one has a question (should only hard bounces unsubscribe people, or soft bounces too?), it asks me while I'm driving. I answer, and the thread keeps going.
When the thread thinks it's ready, it goes through my normal flow. It opens a merge request, my review agents leave comments, and the thread fixes them until it's clean. Then it creates a review environment for me to check myself. At that point I tell Grok Bot to pass on that thread for now, and I finish it at home, when I can look at it with my own eyes.
While one thread is working, you tell Grok Bot to have the god thread start another one. And another. You keep going until one comes back with a question or is ready for you, you answer it, and you start the next one. Since you're driving, there's no email and no messages, just ideas and answers going back and forth with your agents.
Version 1: the easy way (five minutes)
This is how I did it first, and it needs almost no setup.
- Install the Grok Bot desktop app on the computer where T3 Code runs (the one that already reaches all your threads).
- Allow Grok Bot to run commands on that computer.
- Tell it how to use the
t3command:
Use the t3 command line to work with my T3 threads: t3 thread list, t3 thread send <id> "message" --wait, t3 thread show <id>.t3 thread list lists a project's threads (--project picks the project), t3 thread send with --wait waits for the agent and prints its reply, t3 thread show shows a thread's state and latest messages, and t3 thread start starts a new one.
The catch is that Grok Bot can now run any command on that computer, not just t3. And the desktop app has to stay open. That's why I changed it after my first try.
Version 2: Tailscale and the T3 MCP (the one I use now)
Grok Bot has its own computer in the cloud that it runs things on. All my machines are already on Tailscale (that's in the T3 Code setup post too), so I added Grok Bot's computer to my tailnet and let it talk to T3's MCP on my T3 server. Now it reaches my threads directly, and nothing runs on my PC.
1. Turn on Tailscale HTTPS and copy the MCP URL
In T3 Code, go to Settings → Sharing & access and turn on Tailscale HTTPS. Then copy the MCP URL: Settings → Environments → ⋯ → Copy MCP URL. It looks like https://<your-pc>.ts.net:8773/mcp.
2. Put Grok Bot's computer on your tailnet
In Grok Bot, go to Connect apps → Your plugins → Tailscale → Authenticate.
- Pitfall: until you do this, the bot's computer can't reach your PC. It just tells you the computer is unreachable.
- Pitfall: don't tag the new device in Tailscale. Tagging disconnects it.
3. Add T3 as a local connector
Tell Grok Bot:
Add a custom MCP server called t3 that runs: npx -y mcp-remote@0.16.4 https://<your-pc>.ts.net:8773/mcp- Pitfall: give it the command, not the URL. A custom server added as a URL is called from Grok Bot's servers, and those aren't on your tailnet. The command runs on the bot's own computer, which is.
4. Sign in once, in the bot's terminal
Have Grok Bot run the same command in its own terminal:
npx -y mcp-remote@0.16.4 https://<your-pc>.ts.net:8773/mcp- Pitfall: inside the connector, the sign-in gives up after 60 seconds. Do it once in the terminal, then restart the connector after you've signed in.
5. Finish the sign-in on your own device
The bot's own browser can't open the sign-in page on your tailnet, so do this part yourself. Open the sign-in link it prints on any device on your tailnet. It asks for a sign-in code. You get one in T3 under Settings → Sharing & access, or from a terminal on your PC:
t3 auth pairing create --ttl 5mEnter the code, choose Full access and approve. The last step redirects to a localhost link, which fails on your device. That's expected. Copy that failed link and paste it back to Grok Bot, and it hands it to the waiting sign-in.
- Pitfall: pick Full access if your god thread runs with Full access. With Supervised, it can't send to your existing Full-access threads: T3 refuses because the thread would get more access than the connection that's driving it.
The sign-in lasts 30 days. You can revoke it under Settings → Sharing & access.
6. Check that it works
Which t3 tools do you have? Then start a test thread that replies with "pong".Mine listed 71 tools, and the test thread answered "pong from Grok Bot".
7. Turn off command access on your PC
If you did version 1 first, turn off Grok Bot's permission to run commands on your PC. It doesn't need it anymore.
Locking it down
In the video I said you could restrict this further. Here's where I am with that. Grok Bot's computer is now a device on your tailnet, so it can reach every device there, not just T3.
Turning off command access on my PC closed the biggest hole from version 1. Beyond that, I haven't found a supported way to narrow it down yet, and tagging the device (the usual way to give a device its own rules in Tailscale) disconnects it. So for now I treat it like any other device on my tailnet.
Why I stopped typing
I've used this for a few days now, and it's hard to go back to typing. At any point you can stand up, walk around your office or your house, and keep talking to your agent: give it feedback, and tell it to ask you whatever it needs to get unblocked.
It does feel like typing is dying out. We used to type because code had to be exactly the characters we wanted. When you describe a task to an agent, it's not a problem if it mishears something. It figures it out, or it asks.
I've been dictating for months already. What changed is not having to read the replies, just listening to them on a headset. When I read, there's a good chance an email or a message pops up and pulls me away. In a real conversation with a bot it's a lot harder to get distracted.
Where to start
Start with version 1 if you just want to try it. Five minutes is enough to see if working by voice is for you. Move to version 2 once you decide to keep it.
Grok Bot might have a T3 connector by the time you read this. In the video I asked Theo and Julius from the T3 Code team to build one, so if it's there, use that instead.
For the rest of my setup, see my T3 Code setup post. And if you're curious about the product I worked on in the car, have a look at aicms.
Other videos in this series
T3 Code tutorial: my whole setup, every agent on every computer
T3 Code on three machines over Tailscale, linked machines, and the god thread this video builds on.
AI second brain in 15 minutes, with no extra subscriptions
A wiki the AI writes and keeps up to date, so every new session already knows what the last one learned.