PeakWatch · AgentsComing soon · private beta

Approve, answer and steer Claude Code from your wrist.

PeakWatch turns a Galaxy Watch into a thin client for your Claude Code sessions. A small relay on your own machine owns the sessions through the Claude Agent SDK; the watch lists them ranked by what needs you, approves or denies tool permissions against a draining countdown, takes prompts by voice and reads replies back. WiFi or LTE, phone optional.

Get PeakWatch first What it does

Wear OS · Galaxy Watch UltraRelay on your machine, or free-hostedWiFi / LTE · phone optional

What PeakWatch is

Your coding agent, on your wrist.

Claude Code sessions on a Galaxy Watch. See which agent needs you, approve a tool with its arguments in front of you, dictate the next prompt and read the reply, with no phone and no laptop open.

tap to unblock an agent

A blocked session outranks everything on the list and wears the only amber on screen. Tap, read the arguments, approve or deny. The agent is moving again before your sleeve is down.

60 s

then it denies itself

Every permission request carries a countdown drawn on the bezel. Ignore it and the relay denies on your behalf, so an agent can never run something because you were in the shower.

phones in the loop

The watch talks straight to your relay over WiFi or LTE. Leave the phone in the bag, the laptop shut; the sessions keep running on your machine.

Features

What ships in the beta

The high-level map. Every item below is built or in build; the waitlist gets each one as it lands.

Ranked by what needs you

Nine status labels across five states: YOUR TURN, WAITING ON YOU with a live countdown, WORKING, MIRROR · IDLE. The list is sorted by who is blocked, newest first.

Approve with the arguments in front of you

"Approve Write?" is not a question anyone can answer; the file path is. Every request shows the tool, its arguments and the SDK's own reason, with Always, Deny and Say why.

Speak or type

Dictate the next prompt with the mic, or use the mini keyboard when it is a path or a token. Each assistant turn streams to the wrist as it completes.

Six quick replies

continue, yes, no, explain, looks good, try again, pinned under every conversation and coloured by what a tap will actually do: reply, resume, or take over.

Summarise a session

A separate tool-less query over the transcript answers "what happened?" in one screen, and works on mirrored and ended sessions without touching them.

Mirror the terminal

The relay tails every Claude Code transcript on disk, so sessions you started at a keyboard show up too, marked violet. Reply from the watch and the wrist takes the session over.

Your plan, at a glance

Session and weekly limits with reset times, on the session page and under Connected in Settings, so you know before you burn the last hour.

Paired to your relay, and only yours

A bearer token generated on first run, typed once. The socket carries it as a subprotocol so it never lands in a proxy log; ten wrong tokens a minute earns a 429.

Screens

A look inside PeakWatch

Scroll sideways. These are the screens as they exist today.

PeakWatch watch screen: Approve — The tool, the path, the SDK's reason, and an amber ring that drains to an automatic deny. — **Approve**The tool, the path, the SDK's reason, and an amber ring that drains to an automatic deny.

PeakWatch watch screen: Sessions — Ranked by what needs you; violet rows are mirrored from a terminal. — **Sessions**Ranked by what needs you; violet rows are mirrored from a terminal.

PeakWatch watch screen: Needs you — A blocked agent sits at the top with a live countdown. — **Needs you**A blocked agent sits at the top with a live countdown.

PeakWatch watch screen: Speak or type — Dictate a prompt, or open the keyboard for anything spoken badly. — **Speak or type**Dictate a prompt, or open the keyboard for anything spoken badly.

PeakWatch watch screen: Chat — Replies stream to the wrist as each turn completes. — **Chat**Replies stream to the wrist as each turn completes.

PeakWatch watch screen: Quick replies — Six pills, coloured by what a tap does. — **Quick replies**Six pills, coloured by what a tap does.

PeakWatch watch screen: Session page — Both ends of the exchange, and Summarise session. — **Session page**Both ends of the exchange, and Summarise session.

PeakWatch watch screen: Plan usage — Session and weekly limits with reset times. — **Plan usage**Session and weekly limits with reset times.

FAQ

PeakWatch, answered

Does it need a phone?

No. The watch app is standalone on Wear OS and talks to your relay directly over WiFi or LTE. A foreground service keeps the socket alive when the watch is off your wrist.

Where do my sessions and code actually run?

On your machine. The relay is a small Node service you run yourself (or the free-hosted variant), and it drives Claude Code through the Claude Agent SDK. The watch is a thin client: it sees prompts, replies, tool requests and summaries, never your repository.

What happens if I miss an approval?

The relay denies it when the countdown runs out; the default is sixty seconds and the ring on the bezel shows it draining. Nothing runs because you were away.

Can it see sessions I started in a terminal?

Yes. The relay tails the transcript every Claude Code session writes to disk, so terminal sessions appear as mirrors. You can read them, summarise them, and take one over by replying from the watch.

Which watches are supported?

Wear OS 5 watches; built and tested on the Galaxy Watch Ultra, including the rotating bezel, Ongoing Activities on the watch face and the curved chrome.

Which agents does it work with?

Claude Code, through the official Claude Agent SDK. Other agents with a comparable SDK are on the roadmap.

The rest of the suite