Tapproval

Approving Claude Code away from your desk: the options compared

Written by the maker of Tapproval, so read it with that in mind. Every claim about another product links to its source; facts as of 25 September 2026.

Claude Code stops and waits whenever it needs permission. Several tools now let you answer from somewhere other than the terminal. They differ more than their descriptions suggest: some need an account and a server in the middle, some need a particular plan, only a few reach the Apple Watch, and some also drive Codex.

Side by side

TapprovalClaude Remote ControlHappyOmnaraclaude-watch
Price100 answers free, then $5 onceFree app; needs a Pro, Max, Team or Enterprise planFree; long voice sessions paidNo platform fee; managed compute paidFree
Apple WatchWatch app, built for the wristNo watch app; the iPhone notification is mirroredNoYes, in the iOS appWatch and iPhone app
iPhone / Android / webWatch onlyiOS, Android, webiOS, Android, web, MaciOS; others not checkediPhone
AccountNoneclaude.ai accountCreated automatically, no emailRequiredNone
Server in the middleNone of ours: direct, or an encrypted tunnelAnthropic'sHosted relay, self-hostableHosted, self-hostableNone (local network only)
Open sourceThe computer halfNoYes (MIT)Yes (Apache-2.0)Yes (MIT)
CodexNot yetNoYesYesNo (a fork targets Codex)
InstallApp Store + one sentence to Claude CodeBuilt inApp store + happy commandApp store + loginBuild it yourself in Xcode
Risk shown on each promptYes, five tiersNoNoNot checkedNo

Which one fits

How the approval actually travels

All of these rely on the same thing underneath: Claude Code's hooks, or its own Remote Control channel. A tool that answers from outside the terminal uses the PermissionRequest hook, and the decision it prints has a shape that is easy to get wrong. A wrong shape is ignored without an error. How the hook works covers the exact shape.

Sources

Something here out of date or unfair? Write to tapproval@thoughtfulsteward.org and it will be corrected.

Set up Tapproval