Using webAgent

Chatting with an Agent

Updated Jun 5, 2026 · 1 min read

Chat is the heart of the app, and it behaves a little differently from an ordinary
chatbot.

Your work survives anything. When you send a message, the agent's turn runs on
the server as a supervised background job — not in your browser. Leaving the page,
closing the browser, switching sessions, or moving to another device does not stop
it. Only finishing, an explicit stop, or a server restart ends a run. When you come
back — even on a different device — the in-progress answer is right there, rebuilt
from the database, because the answer is written to the database as it streams.

You see every step. A single message can drive several rounds of thinking and
tool use. Each step shows as its own bubble, and a small activity bar above the input
ticks through them ("Turn 2: tool call …"). Click it to expand a panel listing every
tool call this exchange, each one openable to see its arguments and result.

Interrupt and steer, naturally. Send a new message while the agent is still
working and it interrupts the current run, folds in your new message, and the
agent decides whether to stop, change direction, or carry on — there's no keyword
guessing. The Stop button is a clean cancel.

If the server is briefly unreachable, your message isn't lost — it's queued
locally and retried automatically (you'll see a "pending" bubble with retry/dismiss).

Related: Sessions & Conversation History, Attachments & Voice Input,
Suggested Replies & Message Actions, The Agent Loop.

#chat#core#runs