The timeline
Pulse is built around a single persistent chat timeline per user. Unlike tools that isolate each conversation into separate sessions, every event — messages, approvals, task updates, reactions — flows into one continuous thread that the agent reasons over.
One thread, responsive work
The timeline supports both direct conversation and background work.
The Main Agent interprets intent. It reads incoming events, decides what the user actually wants, responds directly when a request is quick, and delegates anything heavy or long-running. It is the conversational surface you interact with.
Background work handles heavier tasks such as research, multi-step automation, and document generation without blocking the conversation. Progress and results post back into the timeline as they happen.
This split keeps the chat responsive. You can keep talking while work proceeds, and completed work appears inline rather than in a separate view.
How events flow
Every interaction is an event appended to the timeline:
| Event type | Origin | Effect |
|---|---|---|
| Message | User or agent | Adds turn to the thread |
| Task update | Background work | Posts status, progress, or result |
| Approval request | Pulse | Pauses a sensitive action pending a decision |
| Reaction | User | Lightweight signal on a prior event |
Because all of these share one timeline, Pulse keeps the full picture visible: what was asked, what is running, what is waiting on you, and what finished.
State and summarization
The visible thread is the record of what happened. As the timeline grows, older spans are summarized so Pulse retains intent and decisions without requiring you to restart the conversation. Relevant memory facts are folded into this working context, so durable knowledge survives even after older messages move out of immediate view.
INFO
The timeline is the source of truth for what you see. Summaries help Pulse keep long-running context usable without making the thread difficult to navigate.
Why a single timeline
A persistent timeline means continuity. The agent does not forget which project you are on between sessions, scheduled tasks report into the same place you started them, and approvals arrive in context next to the action that triggered them. There is one place to look, and one thread of reasoning behind it.
You can pin the messages that matter — decisions, specs, attached files — so they stay one glance away as the thread grows.
