Walkie is a phone call with Mara. You think out loud. She runs a whole team of AI engineers building on your Mac, and real pull requests land while you're still walking. You just jam.
Touch your computer once, for one command. Or never, if Claude Code already answers your phone.
Mara is a partner, not a status bar. She pushes back, scopes the idea, and handles all the team coordination herself. Nothing starts until you say go. Then the builds run in the background and she keeps talking with you.
The second tab is the room where the team actually builds. Mara hands off, an engineer takes it, ships it, reports back. You can watch any time. You never have to.
The whole room runs on a tiny local bus on your Mac. No hosted relay, no account, nothing between you and your team.
The backend runs on your own Mac. Setup is one command, and your own Claude Code does the installing.
Walkie is in open beta on TestFlight. Tap the button, install the app, and you'll point it at your Mac at the end.
Join the beta on TestFlightWalkie's team runs on Claude Code, the same one you already use. Open it on your Mac and paste this. It sets everything up and prints a QR code when it's done.
Set up Walkie on my Mac. One thing first: the setup needs my Anthropic API key for the voice, and it can't ask you when you run it for me — so ask ME for it before you start. I can make one at console.anthropic.com/settings/keys (Create Key, name it walkie, copy the sk-ant string). If I'd rather skip it for now that's fine — everything still installs and pairs, the voice just stays quiet until the key lands in ~/.walkie/config.json.
Then run:
curl -fsSL https://walkie.cc/install | bash
If I gave you a key, write it into ~/.walkie/config.json as "anthropicApiKey" and re-run the installer so the service picks it up. When it finishes it prints a QR code — and saves it as an image at ~/.walkie/pair-qr.png; open that for me if the terminal one isn't scannable — plus a walkie:// pairing link. If I'm at the Mac, tell me when the code is on my screen so I can scan it. If I'm remote, send me the pairing link so I can tap it on my phone.
Walkie — setting up your Mac. Everything runs on this machine. No account, and no key ever leaves your Mac. 1/4 Checking what's here… node v22 ✓ npm + git ✓ claude CLI ✓ 2/4 Downloading Walkie… ✓ 3/4 Installing dependencies… ✓ 4/4 Guided setup. A few questions, then the service starts in the background. Or scan to pair in one tap: ▛▀▀▜ ▞▚ ▛▀▀▜ ▌▓▓▐ ▚▞ ▌▓▓▐ ▙▄▄▟ ▓▒ ▙▄▄▟ ✓ Walkie is running on your Mac. Open the app and scan.
Open Walkie, scan the QR your Mac printed, and that's the whole setup. Say the first thing on your mind and start walking.
Driving Claude Code from your phone already? Then you never touch the computer at all. Send it the same prompt from anywhere, and it sends back a pairing link you just tap.
You'll need a Mac and Claude Code (a Claude Pro or Max subscription). That's what the team builds with.
The operating system for one person
running a company of agents.
I've built the other kind of app. I've been inside companies whose whole business was collecting as much of your data as possible and extracting everything they could from it. I built some of those systems myself. Walkie is the anti-system.
And there's a bigger point than this one app, because Walkie itself was built exactly the way it works: I brain dumped on walks, added my own taste, and this is what landed. I think we need to normalize that. An app is just the manifestation of an idea. It's the canvas we paint on. Making one doesn't require knowing anything about the people who use it, so this one doesn't, and everything runs on machines you own. Ideas can be copied, and that's fine. Because if anyone can build anything with AI, then all any of us really have is ideas and taste.
That's also why the source is public, the app and the backend both. Partly so you can see for yourself that nothing leaves your machine. Mostly so you can clone it and make it yours. Honestly, you could skip us entirely and tell your own AI "I tried this walk-and-talk app, build me one." That's fine. You'll be maintaining it alone, and we'll keep shipping new ideas and features that grow with you. Use ours, use yours. I'd just love to hear how your first walk went.
And this isn't only for developers. The version I can see from here: you hand this to a friend who has never written a line of code, they go for a walk, and they come back with the thing they described. Like they had a senior engineer on the line the whole time, and a team of whoever they wanted behind her.