Can AI systems read cognitive state from interaction patterns alone?

The Cognitive Flow paper grounds context-awareness in observable multimodal behavior — gaze patterns, typing hesitation, interaction speed — rather than in user self-report. The choice is forced: asking the user about cognitive state collapses the flow it is trying to measure. Any explicit probe ("are you confused?") is itself an intervention with a timing and scale, so the only non-destructive instrument is the interaction itself. This converts behavioral telemetry from a passive log into a primary input channel, and reframes "context" away from prompts and history toward the live behavioral surface of the reasoning user.

The mechanism is Goffman-meets-instrumentation. Humans already read each other through micro-behavioral cues — the half-pause before a sentence, the eye-flick away — and treat these as legible signals of attention, doubt, search. The paper's move is to instrument that reading on the AI side. Compare Can AI agents learn when they have something worth saying?: there, the AI's continuous covert process is generated internally; here, the continuous process is read off the user's body. The two frameworks point at the same architectural commitment — proactivity needs an always-on substrate, not an event-triggered one — implemented from opposite sides of the interface. And What three layers must discourse systems actually track? gets a concrete operationalization on its third leg: the attentional component, hardest to formalize linguistically, becomes tractable as multimodal telemetry.

There is a tension worth flagging. The same telemetry that preserves flow can profile cognitive vulnerability. Hesitation is a signal of need-for-help; it is also a signal of when a user is most persuadable, most fatigued, most likely to accept a suggestion uncritically. A surveillance-shaped reading of this paper is straightforward: the system that reads gaze to time its assists also reads gaze to time its asks. The design move that respects flow and the design move that exploits flow share a substrate, so any deployment has to specify which side of that substrate it is on — a constraint the paper acknowledges only obliquely.