How should I approve a coding agent's action from smart glasses?
An approval should identify one proposed action on one target and remain attached to that request. The wearer needs enough context to understand the consequence. “Push this branch to the remote repository?” is more meaningful than an unexplained “Continue?”
Keep the decision attached to its request
The software should match the response to a request identifier and verify that the proposal is still current. If the agent replaces the proposal or the request expires, an old tap must not approve the new action. A visible confirmation should distinguish an input received by the glasses from an action accepted by the host.
We would move decisions requiring a diff, payment details or substantial context to the companion screen. Glasses can make a simple decision convenient; the interface should also make it easy to open the evidence before answering.