Hyperdrift · Field notes
UI
field notes.
How interfaces decide what people must learn, and what changes when an agent can act on the page.
← All field notes
Read →Conversation / Hyperdrift First Officer
The dashboard that speaks first
In a recorded Cargo recovery, a spoken instruction starts the work. First Officer checks the response and reports back, with the evidence still on screen.
Recorded sandbox recovery · 29 September 2026
Read →History and human capability / UI and accessibility
Is UI holding us back?
New interfaces can remove work or move it into checking and correction. A historical argument for judging the whole task.
Historical synthesis
Read →WebMCP and shared state / UI and accessibility
Stop making agents hunt for buttons
WebMCP lets a page expose actions to a browser agent. Radar shows how that can keep the person and agent working in the same place.
Radar implementation and draft specification
Read →Traction / First Officer / UI and accessibility
A spoken promise is not a completed action
A Cargo recovery request becomes an action, a checked result and a spoken report. What this bounded demonstration can teach app designers.
Recorded sandbox demonstration
Read →The future of UI / UI and accessibility
Your work should survive a change of interface
Speak, inspect, correct and continue. A future interface should preserve the task when the person changes how they interact.
Design position and research agenda
Read →A peek into Traction / Traction
Here’s the new deal. UI is for intel. Agents are for operating.
A peek into Traction’s 24 October release: the board shows what the Growth Manager and Builder are doing and what they delivered. The agents do the work. We decide what becomes work.
Our Orchestra board · 24 October 2026