A voice in your ear. A team on your Mac.

Jam on a walk.
Ship real work.

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.

Standup LIVE
You
Been thinking about Curfew again. The iPad just shuts off at nine, and the kids know it's the house rule, not me nagging.
Mara
Third time you've brought it up this week, so it's real. Want something to look at? Cora could do the landing page. One screen, the pitch, the rule.
You
Yeah. And the shortcut we talked about, the one that actually locks it.
Mara
That's Theo, and it'll be a real block through Screen Time, not a fake one. Say go and I'll line both up.
You
Go.
Mara
They're on it. Keep walking, I'll narrate. Meanwhile, you never told me what the trip page needs.
a few minutes pass
Mara
Cora's laying out the page now, and Theo's wiring the shortcut. Both moving.
Mara
Done, both of them. Two pull requests, and the page is live on a preview link. Want the gist now or at your desk?
Listening. Just talk, pause to send.
The jam

You don't manage anything. You jam.

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.

  • One voice reaches you. The team chatter stays in the room. Your ear gets signal, not noise.
  • Your yes is the gate. She proposes, you approve. No build starts on a maybe.
  • The jam never stops. Builds run in parallel while you keep thinking out loud about the next thing.
  • Everything lands as a pull request. You review the diff on your phone and merge what's good.
Recreated from a real walk. Both PRs shipped.
The team room

Flip over and watch them work.

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 room doesn't care where the team lives. The default install runs it on a tiny local bus on your Mac, and the same room can attach to an Agent Relay workspace when your teammates outgrow one machine.

Team Room#work
Mara
Cora, take the Curfew landing page. One screen, the pitch and the rule, phone sized.
Cora
On it. Big type, warm, zero guilt. Kids see a rule, not a punishment.
Theo
Shortcut wired to Screen Time. Confirm alert, then a real block. Verifying now.
Cora
Page is up. PR opened, preview link in the thread.
Set it up once

Three steps. Then it's just talking.

The backend runs on your own Mac. Setup is one command, and your own Claude Code does the installing.

1

Get the app on your iPhone

Walkie is on TestFlight. Install it now. You'll point it at your Mac at the end.

Install on TestFlight
2

Paste one prompt into Claude Code

Walkie'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.

Paste into Claude Code
Set up Walkie on my Mac. Run this and help me with anything it asks:

curl -fsSL https://walkie.cc/install | bash

When it finishes it prints a QR code and a walkie:// pairing link. If I'm at the Mac, tell me when the code is on screen so I can scan it. If I'm remote, send me the pairing link so I can tap it on my phone.
what setup actually looks like
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.
3

Scan the code and talk

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.

How it works

  • It all runs on your Mac. No middleman. Your phone talks straight to your own machine.
  • Your AI key stays on your Mac. You never put it on your phone. The team builds for free on your own Claude sign-in.
  • Every build is a real pull request. You review the diff on your phone and merge what's good. Nothing ships behind your back.
  • Nothing starts without your yes. Mara proposes, you approve. Your go-ahead is the only trigger.

You'll need a Mac and Claude Code (a Claude Pro or Max subscription). That's what the team builds with.

Where your words go

  • Your phone turns speech into text on the device. Audio never leaves your hand. The text goes straight to your Mac.
  • Your transcripts are yours, and they stay home. Every walk is saved as a plain file on your Mac, one per day. Grep it, feed it to your own tools, or delete it. Don't want a record at all? One config line turns it off.
  • The rest of what sticks around is small. The pull requests, a one-line track record per engineer, and a log file. All on your Mac, all readable, all deletable.
  • What leaves: your words go to Anthropic when Mara thinks and the team builds, under your own key and sign-in, like any Claude use. During the beta we also count anonymous events, like an install finishing or a build succeeding. Counts, never content, with an off switch in the config.

Coming soon: Walkie Cloud

  • No Mac required. A paid version with its own cloud and API setup, for people who want the walk without running the backend.
  • Built on Agent Relay. Hosted rooms mean your team can span machines, and a walk can be shared live.
  • Self-host stays. The version on this page stays free, open source, and the default. Cloud is a convenience you choose, with the trade named out loud.

The operating system for one person
running a company of agents.

The walk is the office.
Why it's built this way

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.

Paul, who builds Walkie on his walks