Use case
A developer who lets Claude Code run a long task and steps away from the computer needs to reply to confirmation requests or follow-up questions received on a watch so the task continues instead of stalling on missing input.
The old behaviour is to stay at the terminal watching, or simply let the task sit and handle all confirmations in one batch after returning.
A coding agent stops mid-run waiting for human confirmation; once the person leaves the keyboard the task idles, and on return they must re-read context before pushing it forward.
xOcto's call
Useful problem, weak urgency
The trend is that coding agents now run long autonomous tasks, so the human role shifts from writing code to approving and correcting on demand, which makes 'the person is not at the keyboard' the new break point. A wedge is the high-risk steps that need frequent confirmation, such as deploys, database changes or payment-related edits, building a mobile approve-or-abort entry point rather than moving the whole coding session onto a watch.
Reason to use it
Why users would choose it
Inference: if a wrist reply enters the same session directly, the step removed is 'must return to the computer to unblock', so developers who routinely run long agent tasks and leave their desk would try it; however the public material does not say whether a reply actually advances the task, and there is no usage or retention evidence.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth dissecting. Inference: if a wrist reply enters the same session directly, the step removed is 'must return to the computer to unblock', so developers who routinely run long agent tasks and leave their desk would try it; however the public material does not say whether a reply actually advances the task, and there is no usage or retention evidence.
Entry and what to borrow
The trend is that coding agents now run long autonomous tasks, so the human role shifts from writing code to approving and correcting on demand, which makes 'the person is not at the keyboard' the new break point. A wedge is the high-risk steps that need frequent confirmation, such as deploys, database changes or payment-related edits, building a mobile approve-or-abort entry point rather than moving the whole coding session onto a watch.