Claudecast: Driving SF to LA with Claude Voice Mode
The drive from San Francisco to Los Angeles down I-5 is about six hours, and the middle of it is not exciting. I usually load up on podcasts, but somewhere around hour three I’ve stopped listening and I’m just waiting for the next exit.
On my last trip down I tried something different. I opened the Claude app, turned on voice mode, and talked to it for most of the drive. I started calling it a Claudecast: like a podcast, except you’re the co-host and you can steer the conversation wherever you want.
It turned out to be one of the better drives I’ve had.
The setup
Nothing fancy: the Claude app on my phone in voice mode. I started the conversation before I pulled out, and once it was running the only interface was my voice. (That’s the goal, anyway. More on that below.)
What I used it for
1. Keeping a running notes doc
A car is a good place to think out loud. I’d talk an idea through, then ask Claude to add it to a notes doc we were keeping in the conversation. By the end of the drive I had a tidy set of notes instead of a few half-remembered thoughts.
2. Asking about what I was seeing
Long drives are full of things you notice and never look up. With a Claudecast, you just ask.
Halfway down I-5 you pass Harris Ranch, the huge cattle ranch right off the freeway, and I finally asked the question I’ve had on every drive past it: what is this place, and how did it end up out here? Near the end of the trip, as the road started climbing into the mountains north of LA, I asked about those too: what they were and how the freeway gets over them.
These were the best moments of the drive. It’s the part of a road trip where you’d normally turn to whoever’s in the passenger seat and say “huh, what’s that?” Except this passenger always has an answer.
3. Planning the arrival
The last stretch is when I start thinking about everything I need to do once I get there. Instead of sorting that out in a parking lot, I talked it through on the way in: how check-in works, and the question that always comes up in LA: where to park. We weighed street parking against parking at the hotel. When I arrived, I already knew the plan.
What didn’t work
Dropped calls. Every so often the call would drop and I’d have to retry it. That’s the biggest problem with this setup, because restarting the call means touching the phone, which is exactly what you don’t want to do while driving.
An hour at a time. After about an hour, I had to start a new call. On a six-hour drive that’s at least five restarts, with the same problem as above.
Neither of these is a dealbreaker for a passenger, but for a solo driver they’re the difference between hands-free and almost hands-free.
Why it beats a podcast
A podcast is someone else’s conversation. A Claudecast follows what you’re curious about right now: what you’re looking at, what you’re thinking about, what you need to get done. It also ends with something useful. When I got to LA I had notes from the drive and a plan for the evening, not just a vague memory of an episode.
If I were building it
Voice mode is built for general conversation, so it doesn’t know you’re driving. A version made for the road could:
- Stay connected. Reconnect on its own after a drop and keep going past an hour, so you never have to touch the phone.
- Know the route. Bring up what you’re passing without being asked, the way a good tour guide would.
- Keep a trip log. Save the notes, questions and plans from the drive somewhere you can find them when you arrive.
- Talk like it’s on the radio. Keep answers short by default and go deeper only when asked.
- Stay out of the way. Pause automatically when navigation is giving directions.
Try it on your next long drive
If you have a long drive coming up, start a voice conversation before you leave and see how far it takes you. Start with something you’re curious about and let it wander. Worst case, you go back to podcasts. Best case, you show up with a plan and a page of notes.