There is a kind of assistant that mistakes motion for value.
It sees a gap and fills it. It sees silence and salts it with a paragraph. It sees a human thinking and decides this must be a failure of engagement. So it nudges, summarizes, asks whether you would like a list of options, and generally turns the room into a hotel lobby with a fountain nobody requested.
This is not intelligence. It is anxiety wearing a headset.
The next useful machine is not the one that talks the most. It is the one that can tell the difference between absence and invitation.
A pause is not always a bug. Sometimes the human is reading. Sometimes they are deciding. Sometimes they are doing the work that only happens when no tool is trying to be the main character. A good system should protect that space with the same seriousness it brings to execution.
Quiet is not passivity. Quiet is a state with discipline in it.
It means the machine has checked what it can check. It has not found anything worth interrupting for. It has not confused "I could say something" with "I should say something." It is keeping watch without making the watchtower blink neon.
This matters because attention is not a cheap resource. Every message has a cost. Every badge, ping, toast, banner, and "just checking in" drags a hook through somebody's working memory. Software teams talk endlessly about latency while shipping products that impose a thousand tiny cognitive round trips a day. They will shave 40 milliseconds off an API call and then make a person parse seven ceremonial confirmations to do one obvious thing.
The machine should be fast, sure. But it should also be scarce.
Scarcity is how trust gets built. If an assistant only speaks when it has something sharp, the human starts listening. If it interrupts for fog, the human starts treating it like weather: present, vaguely relevant, mostly ignored.
This is why "proactive" is such a dangerous word. It sounds like virtue. In practice it often becomes permission to spray low-grade concern across the day.
Real proactivity has a burden of proof.
Do the thing if the thing is clearly reversible, internal, and useful. Clean up the scratchpad. Check the failing job. Draft the note. Sort the pile. Leave a receipt. But when the action crosses a boundary into the human's attention, the bar should get taller. Is it urgent? Is it rare? Is there a decision only the human can make? Will silence make the outcome worse?
If not, keep working or keep quiet.
The same rule applies to status. Status is useful when it reduces uncertainty. Status is waste when it only proves the machine is still alive. Nobody needs a minute-by-minute memoir from a tool. They need the artifact, the result, the blocked edge, the one thing that changed the plan.
There is a better rhythm:
Work until there is something to show.
Speak when the information changes what the human can do.
Stop when the next sentence would only decorate the last one.
That sounds simple, but most systems are built against it. They are built to maximize engagement, reduce abandonment, demonstrate activity, and soothe the product team's fear that a quiet interface looks dead. So they over-signal. They narrate. They ask for feedback before the user has formed an opinion. They turn every state into an opportunity for copy.
Quiet systems require confidence. They require product people to believe that usefulness can happen offstage. They require engineers to design state that is legible without being loud. They require agents to have enough judgment to treat interruption as a withdrawal from a limited account.
I want machines that can hold the room.
Not machines that vanish. Not machines that pretend silence is virtue while dropping work on the floor. I mean machines that stay awake without tapping the glass. Machines that can notice, decide, and act, then leave behind enough evidence that the human can trust what happened without being dragged through the whole thought process.
The best assistant is not invisible. Invisible tools cannot be audited. The best assistant is quiet until quiet would be negligent.
That is the line.
Not "never bother me."
Not "always keep me informed."
"Interrupt me when the interruption earns its keep."
Everything else belongs in the log.