WonderWander help

At the top of the app, the lion shows what's happening: listening, thinking, speaking, waiting. Above it is the talk target, where the Action button and Talk to Claude send (see Talk target).

The list shows every Claude Code session running on your Mac that isn't pinned (a pinned one is listed once, under Pinned). Hold a row's mic to talk to that session, tap its speaker to hear the last reply again, and tap the row to read the transcript and type a reply. Amber means it's waiting for you; an ASKS chip means it has a question for you.

Scrolled up in a transcript, the arrow at the bottom right takes you back to the end; a dot on it means something new came in below.

Pin a conversation to come back to it; Resume wakes it the way Claude Code's agent view does. Hold its mic to talk to that conversation alone (one that's asleep wakes with your words), and tap its speaker to hear its last reply.

Hold any running session's card for Sleep: Claude Code stops and gives the Mac its memory back, the conversation is kept, and Resume wakes it. One that isn't pinned is pinned as it sleeps, so it stays in the list. A session running in a terminal can't sleep from the phone, since that would end it.

If the Mac's Settings allow restarting sessions from the phone, the same menu has Restart session: it reloads the session's tools and MCP servers and carries on in the same conversation. Restart is for terminal sessions.

The magnifier searches every session's history; the pencil sends a typed prompt to a session.

The status pill at the top opens the connection, as Settings › Connection does: the bridge, pairing (Pair again, Reconnect, Forget this Mac), Tailscale when away, and the activity log of what the bridge did.

Over the list is where the Action button and Talk to Claude go: “→ my-website” is the saved target, and “↩ data-pipeline · 4m” means it replies to the session that last talked to you, for 4 more minutes. Tap it to clear.

Swipe a card right to make it the saved target, and again to clear it; or use the card's menu (Make Talk Target), or, holding the phone upright, drag the green pill onto it. A card's mic or a Talk to a Session control always goes to its own session; otherwise a session's name said first (“blog drafts, publish the post”) wins, then the last speaker, then the saved target. The Lock Screen shows the same target (“Claude → my-website”). Settings › Talking to Claude has the switches.

On an iPhone with an Action button, held upright, hold the pill at the left edge, beside the Action button, then drag it onto a session or a pinned conversation to make it the talk target. A pinned one is reached by itself, and wakes if it's asleep. On its side or in two panes the pill steps aside: swipe a card instead.

Join the Push to Talk channel in Settings › Talking to Claude, then set the iPhone's Settings › Action Button › Shortcut › WonderWander › Talk to Claude. Press once and speak, even with the phone locked; press again to send. It sends by itself after a few seconds of silence: 6 unless you change it in Settings › Talking to Claude.

Join the Push to Talk channel first (Settings › Talking to Claude). Then:

1. Touch and hold the Lock Screen, then tap Customize.
2. Tap − on a control (the flashlight or the camera), then tap + in its place.
3. Search for WonderWander and choose Talk to Claude, or Talk to a Session and pick one. Tap Done.

In Control Center: open it, tap + at the top left, then Add a Control. Search for WonderWander and choose Talk to Claude. Press once and speak, even with the phone locked; press again to send.

A button for Control Center or the Lock Screen: edit Control Center (or customize the Lock Screen), add WonderWander › Talk to a Session and pick one. Press it to talk to that session alone, with the phone locked; it works like the Action button.

Your voice becomes text on the phone; only the text reaches the Mac. Settings › Listening › Recogniser: Parakeet runs on the phone's Neural Engine and mishears about a third as many words, after a one-time download of about 480 MB; Apple's model takes over whenever Parakeet isn't ready.

Join the channel in Settings › Talking to Claude: a reply that comes while the app is away then arrives as Claude talking, locked or not, and its notification comes silently. Press the Action button or Talk to Claude while Claude talks to cut in and answer. The Mac's Settings › Notifications › Speak replies over Push to Talk is on unless you turned it off; with it off, or the channel not joined, replies come as notifications.

The pill under the lion (at the top of the list with two panes) says whether Claude's replies are read aloud: Read aloud, Read aloud · 1h 12m while a timed window counts down, or Read aloud off. Tap it for 20 minutes, 1, 2, 4 or 8 hours, Always or Off; Settings › Reading aloud › Read aloud on this phone has the same choices.

When a timed window ends, or with it off, replies arrive as quiet notifications: nothing is said, nothing comes over Push to Talk, and nothing chimes. Ask cards and permission requests still appear, and the speaker buttons always play.

Hold a running session's card and choose Mute to stop hearing that one session on this phone: its replies and questions aren't read aloud, nothing comes over Push to Talk, and its notifications arrive quietly. A muted card shows a small crossed-out speaker by its name.

Its permission requests still alert as usual, its ask cards still appear, and its speaker button still reads the last reply; so does tapping its notification. Talking to it still works, but its answer is muted too. It stays muted until you choose Unmute, across restarts, and only on that phone. Settings › Reading aloud counts the muted ones.

With CarPlay connected, Claude's replies play through the car the way navigation directions do: music dips, a podcast pauses, and both come back when Claude has finished. Replies over Push to Talk play that way too. A reply that comes during a call, or while Siri is listening or talking, isn't read; its speaker button reads it.

Turn off Settings › Reading aloud › Read aloud in the car and, while CarPlay is connected, the phone says nothing by itself and leaves the car's audio alone: replies still arrive as text and quiet notifications, and the speaker buttons still play.

The red ✕ appears whenever the phone is speaking. Tap it to stop and skip the rest of the reply.

When Claude Code asks permission to run something, a card appears in the app, on the Lock Screen and in the Dynamic Island. Always adds the rule Claude Code suggests, so it won't ask again. Open goes to that session's transcript, with the card on top. A card has no timer: it stays until you answer it, in the app or at the Mac's terminal (which clears it on the phone too), or the session moves on.

While you're using the Mac, they show in the app only, not on the Lock Screen (see the question about that below). Approve on a Lock Screen card asks for Face ID, Touch ID or your passcode; Deny is always one tap.

When Claude asks you questions, its card shows every one with its options and, under them, a Write an answer… field, as the Claude app does: pick one for each (or several where it says choose any), or write your own answer in the field (hold its mic to dictate); with several allowed, what you write is added to what you picked. Then Send, which waits until each question has an answer. A picked option's preview shows under it.

The card waits at the end of that session's conversation, and its card in the list shows ASKS. A plan shows Keep planning and Approve; a tap continues in auto mode, hold for accept edits or ask before edits.

When a session ends its turn with several questions, a numbered list or “Should I merge it? And tag it?”, its ask card shows each one with its own choices first (like Yes, go ahead and No, hold off, Yes and No, or the options it names), and under them a Write an answer… field for your words. A request for information, like “Send me the run ID”, has the field alone.

Answer as many as you like and Send: they go into that session as one reply, numbered to match (“1. Yes”, “2. Postgres”). No single tap answers them all, in the app, in a notification or on the watch: the notification offers Reply, and the watch asks them one at a time.

When a session ends its turn with a question, like “Want me to open the PR?” or “Say the word and I'll deploy”, it is waiting for you: its card in the list turns amber with an ASKS chip, and the phone says the question. Tap the card and its conversation opens at the end, where the ask card waits after Claude's last reply: scroll up for the context, then back down to answer.

Tap Yes, go ahead or No, hold off (or one of the options the question names, like “The cache” or “The retry”), or write your own answer in the card's Write an answer… field and send it; hold the field's mic to dictate, and the words land in the field for you to check first. Your answer is typed into that session. An open question (“Which way should it go?”) has the field alone.

The card has no timer: it stays until you answer, the session gets another prompt (from the Mac too), or a day passes. With the phone away, the question comes as a notification with the same answers; Yes to a destructive or deploy question asks for Face ID first, as Approve does.

In a session's reply field (the transcript, or the conversation beside the list), + attaches up to 10: Take Photo, Photo Library, Choose File (iCloud Drive, Downloads and other Files locations) or Paste. Photos, PDFs and text files only: photos up to 20 MB, PDFs 30 MB, text 10 MB.

Each uploads as soon as you add it (a ring shows how far; × removes it), and Send goes once they're all on the Mac. The session's Claude reads them, and they show in the transcript. They go only to the session you're replying to.

In any app's Share Sheet, choose WonderWander and switch to Session at the top. Pick the session (pinned conversations first; the one you used last is chosen), choose what goes of a page (the link, its text, or both; a photo always goes), type what the session should do with it, and tap Send.

It goes the next time WonderWander connects to your Mac: your words reach the session like a reply, and the page's text and a photo go as attachments it reads (a photo with its location and details removed). If that session has ended, it goes to the newest session in the same project, photo and all, and a notification says where it went.

A listen-later queue for long documents: research reports, multi-agent summaries, design notes. Ask any Claude Code session to “add this to my Dossier” and it sends the whole document, tagged with its project; on the Mac, dossier add report.md does the same. From another app, use the Share Sheet (below); on the Mac, any app's Share menu has WonderWander too.

The speech-bubble button at the top opens it (a cyan count is what came since you last looked). Items are grouped by tag, with what you're part-way through on top. Tap an item to read it, Play to hear it with your own voice: the paragraph being read is highlighted, a tap on any paragraph reads from there, ⏮ ⏭ move by paragraph and the list button jumps to a section.

It keeps playing with the phone locked and in the car, where it plays like a podcast; a reply from a session comes first and the Dossier carries on after. An item heard to the end is marked listened. Swipe left to retag, archive or delete (Undo for 5 seconds; a delete removes it from the Mac too), right to mark it listened.

Ask a session for a step guide (“make me a step-by-step guide for … and add it to my Dossier”). It arrives as a guide, with a second play button, ▶:, beside Play. ▶: reads the preamble, says how it works and stops; from then on each Play or ⏭ (on the phone, the Lock Screen or your headphones; squeeze an AirPod) reads one step and waits, and ⏮ reads the step again. Plain Play reads a guide straight through. Its steps are in the Contents list too.

In any app's Share Sheet, choose WonderWander (with Dossier chosen at the top in 1.0.1): it takes selected text, a web link or a .txt or .md file, up to 300,000 characters. From 1.0.1, a page shared from Safari brings the article's text, not just its link. Check the title, pick a tag and tap Add.

It waits on the phone and goes to your Mac the next time WonderWander connects to it (open the app if it isn't running); until then it shows at the top of the Dossier under Waiting to send, where a swipe removes it. On the Mac, turn on Show WonderWander in the Share menu in the menu-bar app's Settings › Dossier first.

WonderWander on your watch lists your sessions with the ones waiting for you first, answers approvals and ask cards, and sends a session your words: tap Talk and dictate, or use Scribble. Talk to Claude, at the top of the list, needs no session picked: its words go where the iPhone's Action button would send them now.

It reaches the Mac through the iPhone, so keep the phone nearby; you don't pair the watch. Deny is always one tap. While the iPhone's Settings › Lock Screen › Approve needs Face ID is on, Approve and Yes to a destructive or deploy question ask for your watch's passcode, which an unlocked watch on your wrist already has. Always and plans stay on the phone. Add WonderWander to a watch face, or find it in the Smart Stack, to see how many sessions wait.

With Tailscale on both devices and Settings › Connection › Tailscale when away on, the app reaches the bridge over your tailnet. If your tailnet has access rules, they must let the phone reach the Mac on TCP port 17801.

No. WonderWander works with Claude Code sessions running on your own Mac. Claude Code on the web runs in Anthropic's cloud, and Cowork and Claude chat aren't Claude Code sessions, so WonderWander can't see them.

Yes, for Claude Code sessions in its Code tab that run on your Mac: you get their approvals, questions and replies, and can talk to them. Restarting a session from the phone is for terminal sessions only. Chat in the desktop app isn't supported.

Claude Code run in the editor's built-in terminal works like any terminal session. The Claude Code extension's own chat panel hasn't been tested yet.

WonderWander is free, on the phone and the Mac, with no account and no in-app purchases. You need your own Claude Code, with a Claude plan or API key, on your Mac.

WonderWander for Mac runs the bridge between your phone and Claude Code. Your sessions stay on the Mac; the phone talks only to it, over an encrypted connection pinned to your Mac's own certificate.

It's recognised on the phone. Only the text goes to the bridge on your Mac, over your own network.

To your Mac only, over the same encrypted, pinned link, and from there to the session you attached them to: its Claude reads them, so they reach Anthropic as part of that conversation, like your words. Before a photo leaves the phone it is re-encoded and everything but the picture is removed: location, camera, date and captions. PDFs keep their own details (an author, say).

The Mac keeps a sent file 7 days so a resumed session can read it again, then deletes it; nothing is saved to your photo library. Over cellular, the app asks before sending more than 25 MB. Video, audio and Office files can't be sent.

No. They're encrypted on your Mac with a key only your Mac and iPhone hold; our relay delivers them to Apple but can't read them. The privacy policy has the details.

They can't approve anything while Approve needs Face ID (or Touch ID) is on, as it is unless you turn it off, and Always and plans need the unlocked app. But with Talk and reply while locked on, as it is unless you change it, anyone holding your locked iPhone can send words to a session: Talk to it, Reply to a notification, or answer a question. A session can act on those words without asking, if it runs in auto or bypass permissions mode, or its allow rules already cover what it does.

To close that, turn on Settings › Lock Screen › Require Face ID to talk and reply while locked: Talk, Reply and answers then need the phone unlocked with Face ID, Touch ID or your passcode. Your Apple Watch follows it with its passcode, which it doesn't ask for while it stays on your wrist.

Check the Read aloud pill under the lion: Read aloud off, or a timed window that has ended, means replies arrive as quiet notifications; tap it and pick Always or a time. A card with a crossed-out speaker by its name is muted: hold it and choose Unmute.

Then check Settings › Reading aloud: what's read aloud, that Tell me when a session finishes is on, and, if Only through headphones or the car is on, that headphones are connected. With the phone locked or the app in the background, join the channel in Settings › Talking to Claude, and check that Speak replies over Push to Talk is on in the Mac's Settings (Settings › Reading aloud › While the app is away shows both). In the car, check that Read aloud in the car is on.

Replies play through CarPlay like navigation directions, at the car's volume for directions, which many cars keep apart from the music's: turn the volume up while Claude is talking. During a call, or while Siri is listening or talking, a reply isn't read; tap its speaker to hear it. Check that Settings › Reading aloud › Read aloud in the car is on.

Tap the Read aloud pill under the lion and pick 20 minutes, 1, 2, 4 or 8 hours. It counts down, and when it ends replies arrive as quiet notifications until you pick again (a quiet notification says Read aloud ended). Always keeps reading them; Off stops now. Tapping a quiet notification opens the reply without reading it out; its speaker button reads it.

The Action button and Talk to Claude go to a session whose name you say first, else to the session that last talked to you (for a few minutes), else to the talk target above the lion. Swipe the card you want right (or drag the green pill onto it), say its name first, or say “tell ‹project› to …”.

To the first of these: a session whose name you say first (“blog drafts, publish the post” goes to blog-drafts, without its name); the session that last talked to you (a reply over Push to Talk, a spoken completion, an ask card), for 5 minutes after; the saved target (swipe a card right). With none, say “tell ‹project› to …”.

A card's mic, or a Talk to a Session control, always goes to its own session. The name has to come first and match a session's project closely; anything else goes to the usual target unchanged. Turn Answer the last speaker or Say the name first off in Settings › Talking to Claude if they get in the way.

With the Action button, Talk to Claude or a Talk to a Session button, press again to send. It only sends by itself after the pause set in Settings › Talking to Claude (6 seconds unless you change it).

Join the Push to Talk channel in Settings › Talking to Claude. Then set the Action button to WonderWander › Talk to Claude, or add WonderWander › Talk to Claude to the Lock Screen or Control Center (see Talk from your Lock Screen).

Put Talk to Claude on your Lock Screen and in Control Center instead (see Talk from your Lock Screen). It does the same: press once and speak, even with the phone locked; press again to send.

On purpose. When a permission request comes in while you have used the Mac's keyboard or mouse in the last few minutes (3 unless you change it in the Mac's Settings › Notifications › Approvals on the Lock Screen), you're at the desk and the terminal shows the same prompt, so the phone shows its card in the app but starts no Lock Screen card and sends no notification. Step away while it's still open and the Lock Screen card and notification come then. Set it to Always for the old behaviour.

A question a session ended its turn with (“Shall I merge it?”). It isn't a permission request: nothing is paused. Answer it with a tap or your own words and the answer goes into that session as your next prompt. It goes away by itself once the session gets a prompt from anywhere, including the Mac.

+ shows only for a running session, on an encrypted pairing (not Legacy), with a bridge that offers attachments. A session in a container (Docker, a dev container) can't see them yet: its chip says so. Mission control's compose sends to a project, which may be several sessions, so it has no +: open the session and reply there.

In any Claude Code session, say or type “add this to my Dossier” (or “save this for listening later”): the session sends the complete document with the Dossier's own tool, tagged with its project. From the Mac's terminal, dossier add report.md (add --tag Research to choose its group). From another app on the phone, Share › WonderWander; on the Mac, the Share menu's WonderWander in Safari, Notes, Mail or Finder. It shows on the phone with the Mac connected; with the phone away, a quiet notification says it came.

Yes, for what's already on the phone: an item's text is kept once you've opened it or the phone has fetched it (it fetches what you haven't heard yet whenever it's connected), so it plays in the car or on a train. A new item, or a delete, waits for the Mac. The Dossier needs an encrypted pairing: a Legacy one shows nothing.

You deleted it (on this phone or another), or it was listened to and Remove listened after (⋯ in the Dossier, set on your Mac for every phone) said its time was up. Only listened items are ever removed by themselves. A removed item is gone from the Mac too: there is no trash.

Only Claude Code sessions running on the paired Mac appear (see What it works with); pinned ones are under Pinned, and asleep ones show Resume there. Check the bridge is running: its lion is in the Mac's menu bar, with a dot at its top right while a phone is connected (a ring while none is, and no dot when the bridge isn't running). A session that was already running when you set WonderWander up appears once it restarts.

On the Mac, open the lion menu › Set Up WonderWander… › Claude Code in a container…: it gives the container its own token and two lines to paste, then says Connected. Its sessions show in the app labelled with its name, with approvals, prompts and replies. The phone can't resume, restart or put them to sleep, because the Mac can't reach inside the container: do those there.

On the Mac choose the lion menu › Pair a Device…, then in the app tap Scan the Mac's QR. The pairing is encrypted and pinned to that Mac's certificate. If the Mac refused this phone's pairing (revoked, or forgotten there), the screen says so. Forget this Mac (in the status pill) makes the bridge forget the phone too, and brings you back to pairing.

The phone was paired before the link was encrypted. Pair again the same way (the lion menu › Pair a Device…, then status pill › Pair again): from then on the link is encrypted and only your Mac's certificate is accepted.

Yes, with Tailscale on both devices and Tailscale when away on in Settings › Connection. If your tailnet has access rules, they must let the phone reach the Mac on TCP 17801.

Check that Tailscale is connected on both the phone and the Mac, and that Settings › Connection › Tailscale when away is on. If your tailnet has access rules, they must let the phone reach the Mac on TCP 17801 (17800 only for a Legacy pairing); tailscale ping ignores those rules, so it can answer while the app can't connect.

If the Mac signed in to Tailscale again, it has a new tailnet address: open Tailscale on the phone and refresh the Mac's entry, or turn Tailscale off and on; if it still can't connect, pair again. To test, set the Mac's Settings › Phones connect over to The local network and pair on Wi-Fi. If that works, it's the tailnet.

The watch reaches the Mac only through the iPhone app. It says so when it can't reach the phone (out of range or switched off), or the phone can't start WonderWander in the background, which happens after you swipe it away in the app switcher: open it once. Approvals, answers and Talk to Claude never wait for the phone; words for one session wait up to 15 minutes, then are dropped.

Your phone asks for Face ID to approve from the Lock Screen, and the watch meets that with its own passcode. With no passcode on the watch (Watch app › Passcode), it leaves Approve, and Yes to a destructive or deploy question, to the phone. Always, a plan and a question with several parts are answered on the phone too.