@lotics/app-sdk 0.51.3 → 0.51.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/ai.md +2 -1
- package/package.json +1 -1
package/docs/ai.md
CHANGED
|
@@ -127,10 +127,11 @@ The run's lifetime is decoupled from the stream: the server drives it to complet
|
|
|
127
127
|
|
|
128
128
|
### Sessions
|
|
129
129
|
|
|
130
|
-
`run()` requires `{ sessionId }` — an **app-minted opaque key** grouping runs into a working session. Each run replays the session's prior **completed** runs (their inputs and outputs, including re-materialized image/PDF inputs) as conversation context, so a follow-up like "make it a bit less" resolves against the previous result.
|
|
130
|
+
`run()` requires `{ sessionId }` — an **app-minted opaque key** grouping runs into a working session. Each run replays the session's prior **completed** runs (their inputs and outputs, including re-materialized image/PDF inputs) as conversation context, so a follow-up like "make it a bit less" resolves against the previous result. Three rules keep this sane:
|
|
131
131
|
|
|
132
132
|
- **The app owns the state.** Always pass the authoritative current state in `input` — the session context is memory, not the source of truth.
|
|
133
133
|
- **Mint a new `sessionId` to clear context.** There is no reset call; a fresh key is a fresh session.
|
|
134
|
+
- **One-shot agents get a fresh `sessionId` per run.** Session context only pays for conversational follow-ups. If every run is self-contained (the app passes the complete input each time — e.g. a document-extraction agent), reusing a key replays dead context into every request — every replayed run still bills its input tokens, so a one-shot agent on a shared key pays for history it never uses. Append a per-run nonce to the key instead. (Media itself replays as a provider file reference — uploaded once, referenced by id — so a long session no longer grows toward the provider's request-size cap; the cost of dead context is tokens, not payload.)
|
|
134
135
|
|
|
135
136
|
Sessions are scoped to the authenticated member who ran them: two members using the same `sessionId` string share nothing, and a member can never read or extend another member's thread.
|
|
136
137
|
|