mirror of
https://github.com/vercel/eve.git
synced 2026-09-20 05:35:39 +08:00
Andrew Barba
26 lines
1.6 KiB
Plaintext
26 lines
1.6 KiB
Plaintext
---
|
|
title: "How It Runs"
|
|
description: "Part 2 of the Build an Agent tutorial. Session, turn, and durable steps, and why a turn survives a crash."
|
|
---
|
|
|
|
The analytics assistant sent one message and got one answer. Three terms describe the model behind that.
|
|
|
|
| Term | Meaning |
|
|
| ----------- | ------------------------------------------------- |
|
|
| **session** | Your whole conversation (durable, can span days). |
|
|
| **turn** | One message you send and the work it triggers. |
|
|
| **step** | A durable checkpoint within the turn. |
|
|
|
|
The session runs as one durable workflow, and eve saves each turn's progress at every step. Completed steps never re-run; eve replays the recorded result. A step interrupted mid-execution re-runs, so make non-idempotent side effects like charges or emails idempotent, or gate them with approval. A turn that's waiting on you (an approval, a question) resumes whenever you answer, even if that's much later.
|
|
|
|
That's why the features in the rest of this tutorial work the way they do:
|
|
|
|
- The metric glossary in Step 5 survives across turns. State is checkpointed at step boundaries, so it sticks.
|
|
- The spend approval in Step 7 pauses the turn on your yes/no, then picks up exactly where it left off.
|
|
|
|
You author capabilities, including tools, instructions, channels, and skills. eve drives the model-to-tool loop and decides when a turn continues, waits, or ends. You never write that loop yourself.
|
|
|
|
→ Next: [Step 3: Query sample data](./query-sample-data)
|
|
|
|
Depth: [Execution model & durability](../concepts/execution-model-and-durability)
|