Agent and chat UIs

Agent and chat UIsstreaming, tool calls, interruption, context

An agent runs over time and takes actions, which is a harder UI problem than a chat bubble. The user needs to follow what it’s doing, trust the steps and stop it the moment it goes wrong.

• Streaming so the user sees thinking arrive token by token - silence reads as a hang, even when work is happening.
• Tool-call surfaces that make each action visible: which file it read, what command it ran, what it’s about to change.
• Interruption as a first-class control. A stop button that actually halts the run, immediately, is non-negotiable for trust.
• Context display so the user knows what the agent can see. Hidden context is the fastest way to lose a user’s confidence.