How do smart glasses keep track of several coding agents at once?
Each task needs a stable identity that stays visible in its updates. A project name and short task label help the wearer distinguish parallel work. Without them, an agent's “Done” or “Approve?” message can be mistaken for a different task's result.
Keep separate tasks separate
The interface should keep each task's state and pending decisions independently. Switching to a new task should not transfer a previous approval input or allow a delayed response from the old task to overwrite the screen. We would prioritize requests that need attention while keeping routine progress available on demand.
In an example with “Website: deploy preview” and “App: fix login,” an approval for the preview belongs only to the website task. Clear labels help the person; matching request and task identifiers enforce that separation in the software.