What should a coding-agent update show in smart glasses?
A useful update identifies the project, the task, its current state and the next decision. “Website / checkout form / tests failed / open details” gives the wearer somewhere to act. “Something went wrong” leaves out almost everything needed to understand the interruption.
Write the update around the next action
We give a request for input more space than routine progress. If the agent needs approval, name the proposed action and its target. If it has finished, say what finished and whether validation passed. Keep the complete output available on the host so the short version has evidence behind it.
Imagine two tasks running together: a website build and a documentation edit. “Finished” is ambiguous; “Docs: draft ready to review” is useful even when you have not looked at either task for ten minutes. These are example messages, not reported execution results.
An example update with enough context
These invented messages describe the same sample task at different stages. A compact format can still distinguish waiting, success and failure.
| State | Example wearable message |
|---|---|
| Working | Website / checkout form / running tests |
| Needs input | Website / checkout form / open the preview for review? |
| Failed | Website / checkout form / one test failed / open details |
| Ready | Website / checkout form / changes ready; tests passed / review diff |