Skip to content

Commit 89622b0

Browse files
committed
Improves the session definition
1 parent 3b91999 commit 89622b0

2 files changed

Lines changed: 5 additions & 10 deletions

File tree

apps/webapp/app/components/BlankStatePanels.tsx

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -207,16 +207,14 @@ export function SessionsNone() {
207207
}
208208
>
209209
<Paragraph spacing variant="small">
210-
A session is a pair of streams: input for incoming user messages, and output for
211-
everything the agent produces, including AI generation parts (text, reasoning, tool
212-
calls, etc.) and any custom data parts your task emits. Sessions also orchestrate the
213-
execution of agent runs, so a single conversation can span many task triggers.
210+
A session is a stateful execution of an agent. It includes two-way streaming and durable
211+
compute. A session can have multiple “Runs” associated with it.
214212
</Paragraph>
215213
<Paragraph spacing variant="small">
216214
The easiest way to create one is to trigger a <InlineCode>chat.agent</InlineCode> task,
217215
which is built on sessions and handles the chat turn loop for you. You can also call{" "}
218-
<InlineCode>sessions.start()</InlineCode> directly for non-chat patterns like agent
219-
inboxes, approval flows, or server-to-server streaming.
216+
<InlineCode>sessions.start()</InlineCode> directly for non-chat patterns like agent inboxes,
217+
approval flows, or server-to-server streaming.
220218
</Paragraph>
221219
</InfoPanel>
222220
);

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.sessions._index/route.tsx

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -129,10 +129,7 @@ function SessionsHelpTooltip() {
129129
<div>
130130
<Paragraph variant="small/bright">What is a session?</Paragraph>
131131
<Paragraph variant="small" className="mt-1">
132-
A session is a pair of streams: input for incoming user messages, and output for
133-
everything the agent produces, including AI generation parts (text, reasoning, tool
134-
calls, etc.) and any custom data parts your task emits. Sessions also orchestrate the
135-
execution of agent runs, so a single conversation can span many task triggers.
132+
A session is a stateful execution of an agent. It includes two-way streaming and durable compute. A session can have multiple “Runs” associated with it.
136133
</Paragraph>
137134
</div>
138135
<div className="flex flex-col gap-2.5 border-t border-grid-dimmed pt-3">

0 commit comments

Comments
 (0)